Micron Document
🎖️GitЯра🎖️

Node / meshtastic / Meshtastic-Android / commits / d5d50a9

Commit d5d50a9d4b3842863d540e2e8b5c38411e8d10f8

󰉖 Browse tree at this commit

Parents : 8b7e251
Author : James Rich <2199651+jamesarich@users.noreply.github.com>
Signature : Signature validation error
Date : 2026-08-11T11:09:25-07:00
Committer : GitHub <noreply@github.com>
Date : 2026-08-11T13:09:25-05:00

chore: Scheduled updates (Firmware, Hardware, Translations) (#6609)

Changes

76 files changed, 506 insertions(+), 923 deletions(-)

M core/resources/src/commonMain/composeResources/values-ar/strings.xml -12
M core/resources/src/commonMain/composeResources/values-be/strings.xml -12
M core/resources/src/commonMain/composeResources/values-bg/strings.xml +4 -13
M core/resources/src/commonMain/composeResources/values-ca/strings.xml -12
M core/resources/src/commonMain/composeResources/values-cs/strings.xml +3 -13
M core/resources/src/commonMain/composeResources/values-de/strings.xml +4 -15
M core/resources/src/commonMain/composeResources/values-el/strings.xml -4
M core/resources/src/commonMain/composeResources/values-es/strings.xml -13
M core/resources/src/commonMain/composeResources/values-et/strings.xml +2 -15
M core/resources/src/commonMain/composeResources/values-fi/strings.xml +5 -15
M core/resources/src/commonMain/composeResources/values-fr/strings.xml -14
M core/resources/src/commonMain/composeResources/values-ga/strings.xml -12
M core/resources/src/commonMain/composeResources/values-gl/strings.xml -4
M core/resources/src/commonMain/composeResources/values-hr/strings.xml -2
M core/resources/src/commonMain/composeResources/values-ht/strings.xml -12
M core/resources/src/commonMain/composeResources/values-hu/strings.xml -13
M core/resources/src/commonMain/composeResources/values-it/strings.xml +5 -15
M core/resources/src/commonMain/composeResources/values-ja/strings.xml +5 -15
M core/resources/src/commonMain/composeResources/values-ko/strings.xml -12
M core/resources/src/commonMain/composeResources/values-lt/strings.xml -12
M core/resources/src/commonMain/composeResources/values-nl/strings.xml -12
M core/resources/src/commonMain/composeResources/values-no/strings.xml -12
M core/resources/src/commonMain/composeResources/values-pl/strings.xml -13
M core/resources/src/commonMain/composeResources/values-pt-rBR/strings.xml -13
M core/resources/src/commonMain/composeResources/values-pt/strings.xml -12
M core/resources/src/commonMain/composeResources/values-ro/strings.xml -14
M core/resources/src/commonMain/composeResources/values-ru/strings.xml +5 -15
M core/resources/src/commonMain/composeResources/values-sk/strings.xml -12
M core/resources/src/commonMain/composeResources/values-sl/strings.xml -12
M core/resources/src/commonMain/composeResources/values-sq/strings.xml -12
M core/resources/src/commonMain/composeResources/values-sr/strings.xml -12
M core/resources/src/commonMain/composeResources/values-srp/strings.xml -12
M core/resources/src/commonMain/composeResources/values-sv/strings.xml -14
M core/resources/src/commonMain/composeResources/values-tr/strings.xml -12
M core/resources/src/commonMain/composeResources/values-uk/strings.xml -14
M core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml +5 -15
M core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml -14
M docs/ar-rSA/user/messages-and-channels.md +12 -12
M docs/be-rBY/user/messages-and-channels.md +12 -12
M docs/bg-rBG/user/messages-and-channels.md +12 -12
M docs/ca-rES/user/messages-and-channels.md +12 -12
M docs/cs-rCZ/user/messages-and-channels.md +12 -12
M docs/de-rDE/user/messages-and-channels.md +12 -12
M docs/el-rGR/user/messages-and-channels.md +12 -12
M docs/es-rES/user/messages-and-channels.md +12 -12
M docs/et-rEE/user/messages-and-channels.md +12 -12
M docs/fi-rFI/user/messages-and-channels.md +12 -12
M docs/fr-rFR/user/messages-and-channels.md +12 -12
M docs/ga-rIE/user/messages-and-channels.md +12 -12
M docs/gl-rES/user/messages-and-channels.md +12 -12
M docs/hr-rHR/user/messages-and-channels.md +12 -12
M docs/ht-rHT/user/messages-and-channels.md +12 -12
M docs/hu-rHU/user/messages-and-channels.md +12 -12
M docs/is-rIS/user/messages-and-channels.md +12 -12
M docs/it-rIT/user/messages-and-channels.md +12 -12
M docs/iw-rIL/user/messages-and-channels.md +12 -12
M docs/ja-rJP/user/messages-and-channels.md +12 -12
M docs/ko-rKR/user/messages-and-channels.md +12 -12
M docs/lt-rLT/user/messages-and-channels.md +12 -12
M docs/nl-rNL/user/messages-and-channels.md +12 -12
M docs/no-rNO/user/messages-and-channels.md +12 -12
M docs/pl-rPL/user/messages-and-channels.md +12 -12
M docs/pt-rBR/user/messages-and-channels.md +12 -12
M docs/pt-rPT/user/messages-and-channels.md +12 -12
M docs/ro-rRO/user/messages-and-channels.md +12 -12
M docs/ru-rRU/user/messages-and-channels.md +12 -12
M docs/sk-rSK/user/messages-and-channels.md +12 -12
M docs/sl-rSI/user/messages-and-channels.md +12 -12
M docs/sq-rAL/user/messages-and-channels.md +12 -12
M docs/sr-rLatn/user/messages-and-channels.md +12 -12
M docs/srp/user/messages-and-channels.md +12 -12
M docs/sv-rSE/user/messages-and-channels.md +12 -12
M docs/tr-rTR/user/messages-and-channels.md +12 -12
M docs/uk-rUA/user/messages-and-channels.md +12 -12
M docs/zh-rCN/user/messages-and-channels.md +12 -12
M docs/zh-rTW/user/messages-and-channels.md +12 -12

Diff

diff --git a/core/resources/src/commonMain/composeResources/values-ar/strings.xml b/core/resources/src/commonMain/composeResources/values-ar/strings.xml
index a9d7901e13..373e42d68a 100644
--- a/core/resources/src/commonMain/composeResources/values-ar/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-ar/strings.xml
@@ -197,22 +197,10 @@
<string name="reset_to_defaults">العودة إلى الإعدادات الأصلية</string>
<!-- ROLE -->
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">المفتاح المؤقت غير جيد</string>
- <string name="routing_error_admin_public_key_unauthorized">المفتاح العام غير مسموح</string>
- <string name="routing_error_bad_request">طلب غير جيد</string>
- <string name="routing_error_duty_cycle_limit">عدد الرسائل تعدى الحد المخصص في منطقتك</string>
<string name="routing_error_got_nak">لم يستلم</string>
- <string name="routing_error_max_retransmit">وصول حد الإرسال الأعلى</string>
- <string name="routing_error_no_channel">لا يوجد قناه</string>
- <string name="routing_error_no_interface">لم يجد وسيط</string>
- <string name="routing_error_no_response">لا يوجد رد</string>
<string name="routing_error_no_route">لاطريق</string>
<string name="routing_error_none">استلم</string>
- <string name="routing_error_not_authorized">غير مسموح</string>
- <string name="routing_error_pki_failed">فشل إرسال التشفير</string>
- <string name="routing_error_pki_unknown_pubkey">المفتاح العام غير معروف</string>
<string name="routing_error_timeout">استغرق وقت طويل</string>
- <string name="routing_error_too_large">رسالة كبيره</string>
<string name="rssi">مؤشر القوة النسبية</string>
<!-- SAVE -->
<string name="save">حفظ</string>

diff --git a/core/resources/src/commonMain/composeResources/values-be/strings.xml b/core/resources/src/commonMain/composeResources/values-be/strings.xml
index e86900ec07..c52d7c195b 100644
--- a/core/resources/src/commonMain/composeResources/values-be/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-be/strings.xml
@@ -239,22 +239,10 @@
<string name="role_tak_desc">Аптымізавана для сувязі з сістэмай ATAK, змяншае руцінныя трансляцыі.</string>
<string name="role_tracker_desc">Транслюе пакеты з GPS-каардынатамі з высокім прыярытэтам.</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Няправільны ключ сесіі</string>
- <string name="routing_error_admin_public_key_unauthorized">Адкрыты ключ не аўтарызаваны</string>
- <string name="routing_error_bad_request">Няправільны запыт</string>
- <string name="routing_error_duty_cycle_limit">Дасягнута рэгіянальнае абмежаванне каэфіцыента працы</string>
<string name="routing_error_got_nak">Атрымана адмоўнае пацвярджэнне</string>
- <string name="routing_error_max_retransmit">Дасягнута максімальная колькасць паўторных перадач</string>
- <string name="routing_error_no_channel">Няма канала</string>
- <string name="routing_error_no_interface">Няма інтэрфейсу</string>
- <string name="routing_error_no_response">Няма адказу</string>
<string name="routing_error_no_route">Няма маршруту</string>
<string name="routing_error_none">Пацверджана</string>
- <string name="routing_error_not_authorized">Не аўтарызавана</string>
- <string name="routing_error_pki_failed">Зашыфраваная адпраўка не атрымалася</string>
- <string name="routing_error_pki_unknown_pubkey">Невядомы адкрыты ключ</string>
<string name="routing_error_timeout">Скончыўся час чакання</string>
- <string name="routing_error_too_large">Пакет занадта вялікі</string>
<string name="rssi">адносная магутнасць</string>
<!-- SAVE -->
<string name="save">Запісаць</string>

diff --git a/core/resources/src/commonMain/composeResources/values-bg/strings.xml b/core/resources/src/commonMain/composeResources/values-bg/strings.xml
index 21ced3c743..00e730aea0 100644
--- a/core/resources/src/commonMain/composeResources/values-bg/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-bg/strings.xml
@@ -690,7 +690,6 @@
<string name="message_delivery_status">Състояние на доставка на съобщението</string>
<string name="message_device_managed">Това радио се управлява и може да бъде променяно само от отдалечен администратор.</string>
<string name="message_input_label">Съобщение</string>
- <string name="message_routing_error_no_channel">Няма избран канал</string>
<string name="message_routing_error_pki_failed">Не можа да се изпрати криптирано съобщение</string>
<string name="message_routing_error_pki_send_fail_public_key">Ключът на получателя не е наличен</string>
<string name="message_routing_error_pki_unknown_pubkey">Получателят се нуждае от вашия ключ</string>
@@ -995,21 +994,13 @@
<string name="role_tracker_desc">Излъчва приоритетно пакети за GPS позиция</string>
<string name="rotary_encoder_1_enabled">Ротационен енкодер #1 е активиран</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Невалиден ключ за сесия</string>
- <string name="routing_error_admin_public_key_unauthorized">Публичният ключ е неоторизиран</string>
- <string name="routing_error_bad_request">Невалидна заявка</string>
- <string name="routing_error_duty_cycle_limit">Достигнат е регионален лимит на работния цикъл</string>
<string name="routing_error_got_nak">Получено отрицателно потвърждение</string>
- <string name="routing_error_max_retransmit">Достигнат максимален брой препращания</string>
- <string name="routing_error_no_channel">Няма канал</string>
- <string name="routing_error_no_interface">Няма интерфейс</string>
- <string name="routing_error_no_response">Няма отговор</string>
<string name="routing_error_no_route">Няма маршрут</string>
<string name="routing_error_none">Признато</string>
- <string name="routing_error_not_authorized">Не е оторизиран</string>
- <string name="routing_error_pki_failed">Провалено шифрирано изпращане</string>
- <string name="routing_error_pki_unknown_pubkey">Неизвестен публичен ключ</string>
- <string name="routing_error_too_large">Пакетът е твърде голям</string>
+ <string name="routing_error_pki_failed">Не можа да се изпрати криптирано съобщение</string>
+ <string name="routing_error_pki_send_fail_public_key">Ключът на получателя не е наличен</string>
+ <string name="routing_error_pki_unknown_pubkey">Получателят се нуждае от вашия ключ</string>
+ <string name="routing_error_too_large">Съобщението е твърде голямо за изпращане</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Индикатор за силата на получения сигнал - измерване, използвано за определяне на нивото на получения сигнал, приемано от антената. По-високата стойност на RSSI обикновено показва по-силна и по-стабилна връзка.</string>
<string name="rsyslog_server">rsyslog сървър</string>

diff --git a/core/resources/src/commonMain/composeResources/values-ca/strings.xml b/core/resources/src/commonMain/composeResources/values-ca/strings.xml
index 9c2d0ee163..d316d89e4d 100644
--- a/core/resources/src/commonMain/composeResources/values-ca/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-ca/strings.xml
@@ -218,22 +218,10 @@
<string name="role_tak_tracker_desc">Activa les difusions automàtiques TAK PLI i redueix les difusions rutinàries.</string>
<string name="role_tracker_desc">Difon paquets de posició GPS com a prioritat</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Clau de sessió incorrecta</string>
- <string name="routing_error_admin_public_key_unauthorized">Clau Pública no autoritzada</string>
- <string name="routing_error_bad_request">Sol·licitud errònia.</string>
- <string name="routing_error_duty_cycle_limit">Límit regional de cicle de servei assolit</string>
<string name="routing_error_got_nak">Rebuda confirmació negativa</string>
- <string name="routing_error_max_retransmit">Màx. retransmissions assolides</string>
- <string name="routing_error_no_channel">Sense canal</string>
- <string name="routing_error_no_interface">Sense Interfície</string>
- <string name="routing_error_no_response">Sense resposta</string>
<string name="routing_error_no_route">Sense ruta</string>
<string name="routing_error_none">Confirmat</string>
- <string name="routing_error_not_authorized">No Autoritzat</string>
- <string name="routing_error_pki_failed">Falla d'encriptació</string>
- <string name="routing_error_pki_unknown_pubkey">Clau Pública Desconeguda</string>
<string name="routing_error_timeout">Temps esgotat</string>
- <string name="routing_error_too_large">Packet massa llarg</string>
<!-- SAVE -->
<string name="save">Desar</string>
<string name="save_changes">Desar</string>

diff --git a/core/resources/src/commonMain/composeResources/values-cs/strings.xml b/core/resources/src/commonMain/composeResources/values-cs/strings.xml
index 1f48226e28..f644393cc7 100644
--- a/core/resources/src/commonMain/composeResources/values-cs/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-cs/strings.xml
@@ -1101,23 +1101,13 @@
<string name="root_topic">Kořenové téma</string>
<string name="rotary_encoder_1_enabled">Rotační enkodér #1 povolen</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Špatný klíč relace</string>
- <string name="routing_error_admin_public_key_unauthorized">Veřejný klíč není autorizován</string>
- <string name="routing_error_bad_request">Špatný požadavek</string>
- <string name="routing_error_duty_cycle_limit">Dosažen regionální časový limit</string>
<string name="routing_error_got_nak">Obdrženo negativní potvrzení</string>
- <string name="routing_error_max_retransmit">Dosaženo max. počet přeposlání</string>
- <string name="routing_error_no_channel">Žádný kanál</string>
- <string name="routing_error_no_interface">Žádné rozhraní</string>
- <string name="routing_error_no_response">Žádná odpověď</string>
+ <string name="routing_error_max_retransmit">Nepodařilo se doručit do mesh sítě</string>
<string name="routing_error_no_route">Žádná trasa</string>
<string name="routing_error_none">Potvrzený příjem</string>
- <string name="routing_error_not_authorized">Neautorizovaný</string>
- <string name="routing_error_pki_failed">Chyba při poslání šifrované zprávy</string>
- <string name="routing_error_pki_send_fail_public_key">Odeslání PKI selhalo, chybí veřejný klíč.</string>
- <string name="routing_error_pki_unknown_pubkey">Neznámý veřejný klíč</string>
+ <string name="routing_error_pki_failed">Nepodařilo se odeslat šifrovanou zprávu</string>
<string name="routing_error_timeout">Vypršel čas spojení</string>
- <string name="routing_error_too_large">Příliš velký paket</string>
+ <string name="routing_error_too_large">Zpráva je příliš dlouhá pro odeslání</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Indikátor síly přijímaného signálu, měření, které se používá k určení hladiny výkonu přijímané anténou. Vyšší hodnota RSSI obvykle znamená silnější a stabilnější spojení.</string>
<string name="rsyslog_server">rsyslog server</string>

diff --git a/core/resources/src/commonMain/composeResources/values-de/strings.xml b/core/resources/src/commonMain/composeResources/values-de/strings.xml
index f97be056bd..ddbff82918 100644
--- a/core/resources/src/commonMain/composeResources/values-de/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-de/strings.xml
@@ -949,7 +949,6 @@
<string name="message_delivery_status">Zustellungsstatus für Nachrichten</string>
<string name="message_device_managed">Dieses Radio wird verwaltet und kann nur durch Fernverwaltung geändert werden.</string>
<string name="message_input_label">Nachricht</string>
- <string name="message_routing_error_no_channel">Kein Kanal ausgewählt</string>
<string name="message_routing_error_pki_failed">Konnte verschlüsselte Nachricht nicht senden</string>
<string name="message_routing_error_pki_send_fail_public_key">Empfängerschlüssel nicht verfügbar</string>
<string name="message_routing_error_pki_unknown_pubkey">Empfänger benötigt deinen Schlüssel</string>
@@ -1339,24 +1338,14 @@
<string name="rotary_encoder_1_enabled">Drehencoder #1 aktiviert</string>
<string name="router_role_confirmation_text">Ich habe die &lt;a href="https://meshtastic.org/docs/configuration/radio/device/#roles"&gt; Dokumentation der Geräterollen &lt;/a&gt; und den dazugehörigen Blogeintrag &lt;a href="http://meshtastic.org/blog/choosing-the-right-device-role"&gt; über die Auswahl der richtigen Geräterolle&lt;/a&gt; gelesen.</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Fehlerhafter Sitzungsschlüssel</string>
- <string name="routing_error_admin_public_key_unauthorized">Öffentlicher Schlüssel nicht autorisiert</string>
- <string name="routing_error_bad_request">Ungültige Anfrage</string>
- <string name="routing_error_duty_cycle_limit">Regionale Grenze des Betriebszyklus erreicht</string>
<string name="routing_error_got_nak">negative Bestätigung erhalten</string>
- <string name="routing_error_max_retransmit">Maximale Weiterleitungen erreicht</string>
- <string name="routing_error_no_channel">Kein Kanal</string>
- <string name="routing_error_no_interface">Keine Schnittstelle</string>
- <string name="routing_error_no_response">Keine Reaktion</string>
<string name="routing_error_no_route">Keine Route</string>
<string name="routing_error_none">Bestätigt</string>
- <string name="routing_error_not_authorized">Nicht autorisiert</string>
- <string name="routing_error_pki_failed">Verschlüsseltes Senden fehlgeschlagen</string>
- <string name="routing_error_pki_send_fail_public_key">PKI senden fehlgeschlagen, kein öffentlicher Schlüssel</string>
- <string name="routing_error_pki_unknown_pubkey">Unbekannter öffentlicher Schlüssel</string>
- <string name="routing_error_rate_limit_exceeded">Sendebegrenzung überschritten. Bitte versuchen Sie es später erneut.</string>
+ <string name="routing_error_pki_failed">Konnte verschlüsselte Nachricht nicht senden</string>
+ <string name="routing_error_pki_send_fail_public_key">Empfängerschlüssel nicht verfügbar</string>
+ <string name="routing_error_pki_unknown_pubkey">Empfänger benötigt deinen Schlüssel</string>
<string name="routing_error_timeout">Zeitüberschreitung</string>
- <string name="routing_error_too_large">Nachricht zu groß</string>
+ <string name="routing_error_too_large">Nachricht ist zu groß zum Senden</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Indikator für die empfangene Signalstärke, eine Messung zur Bestimmung der von der Antenne empfangenen Leistungsstärke. Ein höherer RSSI-Wert weist im Allgemeinen auf eine stärkere und stabilere Verbindung hin.</string>
<string name="rsyslog_server">rsyslog Server</string>

diff --git a/core/resources/src/commonMain/composeResources/values-el/strings.xml b/core/resources/src/commonMain/composeResources/values-el/strings.xml
index c4f0a12926..fb641dc9d3 100644
--- a/core/resources/src/commonMain/composeResources/values-el/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-el/strings.xml
@@ -224,10 +224,6 @@
<string name="reset_to_defaults">Επαναφορά προεπιλογών</string>
<!-- ROLE -->
<!-- ROUTING -->
- <string name="routing_error_bad_request">Εσφαλμένο Αίτημα</string>
- <string name="routing_error_max_retransmit">Max. Anzahl Wiederholungen erreicht</string>
- <string name="routing_error_no_channel">Kein Kanal</string>
- <string name="routing_error_pki_unknown_pubkey">Άγνωστο Δημόσιο Κλειδί</string>
<string name="routing_error_timeout">Λήξη χρονικού ορίου</string>
<!-- SAVE -->
<string name="save">Αποθήκευση</string>

diff --git a/core/resources/src/commonMain/composeResources/values-es/strings.xml b/core/resources/src/commonMain/composeResources/values-es/strings.xml
index 0544c1d752..05d36025a5 100644
--- a/core/resources/src/commonMain/composeResources/values-es/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-es/strings.xml
@@ -736,23 +736,10 @@ Estos datos de ubicación pueden ser utilizados para fines como aparecer en un m
<string name="root_topic">Tema raíz</string>
<string name="rotary_encoder_1_enabled">Encoder Número 1 Activado</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Mala clave de sesión</string>
- <string name="routing_error_admin_public_key_unauthorized">Clave pública no autorizada</string>
- <string name="routing_error_bad_request">Solicitud errónea</string>
- <string name="routing_error_duty_cycle_limit">Se alcanzó el límite regional de ciclos de trabajo</string>
<string name="routing_error_got_nak">Recibido un reconocimiento negativo</string>
- <string name="routing_error_max_retransmit">Máximo número de retransmisiones alcanzado</string>
- <string name="routing_error_no_channel">No hay canal</string>
- <string name="routing_error_no_interface">Sin interfaz</string>
- <string name="routing_error_no_response">Sin respuesta</string>
<string name="routing_error_no_route">Sin ruta</string>
<string name="routing_error_none">Reconocido</string>
- <string name="routing_error_not_authorized">No autorizado</string>
- <string name="routing_error_pki_failed">Envío cifrado fallido</string>
- <string name="routing_error_pki_unknown_pubkey">Clave pública desconocida</string>
- <string name="routing_error_rate_limit_exceeded">Límite de tasa excedido. Por favor intente de nuevo más tarde.</string>
<string name="routing_error_timeout">Tiempo agotado</string>
- <string name="routing_error_too_large">Paquete demasiado largo</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Indicador de Fuerza de Señal Recibida (RSSI en inglés), una medida utilizada para determinar el nivel de potencia que está siendo recibido por la antena. Un valor de RSSI más alto generalmente indica una conexión más fuerte y estable.</string>
<string name="rsyslog_server">Servidor rsyslog</string>

diff --git a/core/resources/src/commonMain/composeResources/values-et/strings.xml b/core/resources/src/commonMain/composeResources/values-et/strings.xml
index fa78e9118c..6ab02842c8 100644
--- a/core/resources/src/commonMain/composeResources/values-et/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-et/strings.xml
@@ -1055,7 +1055,6 @@
<string name="message_delivery_status">Sõnumi edastamise olek</string>
<string name="message_device_managed">Seda raadio on hallatud ja muudab ainult kaughaldur.</string>
<string name="message_input_label">Sõnum</string>
- <string name="message_routing_error_no_channel">Kanalit pole valitud</string>
<string name="message_routing_error_pki_send_fail_public_key">Saaja võti pole saadaval</string>
<string name="message_routing_error_pki_unknown_pubkey">Saaja vajab sinu võtit</string>
<string name="message_status_delivered">Kärgvõrku kohale jõudnud</string>
@@ -1452,24 +1451,12 @@
<string name="rotary_encoder_1_enabled">Pöördvalik #1 lubatud</string>
<string name="router_role_confirmation_text">Olen lugenud &lt;a href="https://meshtastic.org/docs/configuration/radio/device/#roles"&gt;Seadme rolli dokumenti&lt;/a&gt; ja blogi postitust &lt;a href="http://meshtastic.org/blog/choosing-the-right-device-role"&gt; Kuidas valida seadmele õige roll&lt;/a&gt;.</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Vigane sessiooni võti</string>
- <string name="routing_error_admin_public_key_unauthorized">Avalik võti autoriseerimata</string>
- <string name="routing_error_bad_request">Vigane päring</string>
- <string name="routing_error_duty_cycle_limit">Piirkondlik töötsükli piirang saavutatud</string>
<string name="routing_error_got_nak">Negatiivne kinnitus</string>
- <string name="routing_error_max_retransmit">Maksimaalne kordusedastus on saavutatud</string>
- <string name="routing_error_no_channel">Kanalit pole</string>
- <string name="routing_error_no_interface">Liidest pole</string>
- <string name="routing_error_no_response">Vastust pole</string>
<string name="routing_error_no_route">Marsruuti pole</string>
<string name="routing_error_none">Kinnitatud</string>
- <string name="routing_error_not_authorized">Autoriseerimata</string>
- <string name="routing_error_pki_failed">Krüpteeritud saatmine nurjus</string>
- <string name="routing_error_pki_send_fail_public_key">PKI saatmine ebaõnnestus, avalikku võtit pole</string>
- <string name="routing_error_pki_unknown_pubkey">Tundmatu avalik võti</string>
- <string name="routing_error_rate_limit_exceeded">Limiit ületatud. Proovi hiljem uuesti.</string>
+ <string name="routing_error_pki_send_fail_public_key">Saaja võti pole saadaval</string>
+ <string name="routing_error_pki_unknown_pubkey">Saaja vajab sinu võtit</string>
<string name="routing_error_timeout">Aegunud</string>
- <string name="routing_error_too_large">Liiga suur pakett</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Vastuvõetud signaali tugevuse indikaator (RSSI), mõõt mida kasutatakse antenni poolt vastuvõetava võimsustaseme määramiseks. Kõrgem RSSI väärtus näitab üldiselt tugevamat ja stabiilsemat ühendust.</string>
<string name="rsyslog_server">rsyslog server</string>

diff --git a/core/resources/src/commonMain/composeResources/values-fi/strings.xml b/core/resources/src/commonMain/composeResources/values-fi/strings.xml
index 69d2906310..e70da958e6 100644
--- a/core/resources/src/commonMain/composeResources/values-fi/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-fi/strings.xml
@@ -1059,7 +1059,6 @@
<string name="message_device_managed">Tätä radiota hallitaan etänä, ja sitä voi muuttaa vain etähallinnassa oleva ylläpitäjä.</string>
<string name="message_input_label">Viesti</string>
<string name="message_routing_error_max_retransmit">Toimitus mesh-verkkoon epäonnistui</string>
- <string name="message_routing_error_no_channel">Kanavaa ei ole valittu</string>
<string name="message_routing_error_pki_failed">Salattua viestiä ei voitu lähettää</string>
<string name="message_routing_error_pki_send_fail_public_key">Vastaanottajan avain ei ole käytettävissä</string>
<string name="message_routing_error_pki_unknown_pubkey">Vastaanottaja tarvitsee avaimesi</string>
@@ -1458,24 +1457,15 @@
<string name="rotary_encoder_1_enabled">Kiertovalitsin #1 käytössä</string>
<string name="router_role_confirmation_text">Olen lukenut &lt;a href="https://meshtastic.org/docs/configuration/radio/device/#roles"&gt;dokumentaation&lt;/a&gt; sekä blogikirjoituksen &lt;a href="http://meshtastic.org/blog/choosing-the-right-device-role"&gt;Choosing The Right Device Role&lt;/a&gt;.</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Virheellinen istuntoavain</string>
- <string name="routing_error_admin_public_key_unauthorized">Julkinen avain ei ole valtuutettu</string>
- <string name="routing_error_bad_request">Virheellinen pyyntö</string>
- <string name="routing_error_duty_cycle_limit">Alueellisen toimintasyklin raja saavutettu</string>
<string name="routing_error_got_nak">Vastaanotettu kielteinen vahvistus</string>
- <string name="routing_error_max_retransmit">Maksimimäärä uudelleenlähetyksiä saavutettu</string>
- <string name="routing_error_no_channel">Ei Kanavaa</string>
- <string name="routing_error_no_interface">Ei Käyttöliittymää</string>
- <string name="routing_error_no_response">Ei vastausta</string>
+ <string name="routing_error_max_retransmit">Toimitus mesh-verkkoon epäonnistui</string>
<string name="routing_error_no_route">Ei reittiä</string>
<string name="routing_error_none">Vahvistettu</string>
- <string name="routing_error_not_authorized">Ei oikeuksia</string>
- <string name="routing_error_pki_failed">Salatun viestin lähetys epäonnistui</string>
- <string name="routing_error_pki_send_fail_public_key">PKI-lähetys epäonnistui, julkinen avain puuttu</string>
- <string name="routing_error_pki_unknown_pubkey">Tuntematon julkinen avain</string>
- <string name="routing_error_rate_limit_exceeded">Käyttöraja ylitetty. Yritä myöhemmin uudelleen.</string>
+ <string name="routing_error_pki_failed">Salattua viestiä ei voitu lähettää</string>
+ <string name="routing_error_pki_send_fail_public_key">Vastaanottajan avain ei ole käytettävissä</string>
+ <string name="routing_error_pki_unknown_pubkey">Vastaanottaja tarvitsee avaimesi</string>
<string name="routing_error_timeout">Aikakatkaisu</string>
- <string name="routing_error_too_large">Paketti on liian suuri</string>
+ <string name="routing_error_too_large">Viesti on liian suuri lähetettäväksi</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Vastaanotetun signaalin voimakkuusindikaattori (RSSI) on mittari, jota käytetään määrittämään antennilla vastaanotetun signaalin voimakkuus. Korkeampi RSSI-arvo yleensä osoittaa vahvemman ja vakaamman yhteyden.</string>
<string name="rsyslog_server">rsyslog-palvelin</string>

diff --git a/core/resources/src/commonMain/composeResources/values-fr/strings.xml b/core/resources/src/commonMain/composeResources/values-fr/strings.xml
index c0c8b7be0a..fe4ca4e167 100644
--- a/core/resources/src/commonMain/composeResources/values-fr/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-fr/strings.xml
@@ -1126,24 +1126,10 @@
<string name="rotary_encoder_1_enabled">Encodeur rotatif #1 activé</string>
<string name="router_role_confirmation_text">J'ai lu la &lt;a href="https://meshtastic.org/docs/configuration/radio/device/#roles"&gt;Documentation du rôle de l'appareil&lt;/a&gt; et le billet de blog sur comment &lt;a href="http://meshtastic.org/blog/choosing-the-right-device-role"&gt;Choisir le rôle de l'appareil approprié&lt;/a&gt;.</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Mauvaise clé de session</string>
- <string name="routing_error_admin_public_key_unauthorized">Clé publique non autorisée</string>
- <string name="routing_error_bad_request">Mauvaise requête</string>
- <string name="routing_error_duty_cycle_limit">Limite du temps d'émission autorisé par heure (duty cycle) atteinte</string>
<string name="routing_error_got_nak">Accusé de réception négatif</string>
- <string name="routing_error_max_retransmit">Nombre de retransmissions atteint</string>
- <string name="routing_error_no_channel">Pas de canal ou d'autorisation</string>
- <string name="routing_error_no_interface">Pas d'interface</string>
- <string name="routing_error_no_response">Aucune réponse</string>
<string name="routing_error_no_route">Pas de routage</string>
<string name="routing_error_none">Entendu par un autre nœud (mais dans le cas d'un message direct, nous n'avons pas reçu la confirmation de réception par le destinataire : soit il n'a pas reçu le message, soit sa confirmation ne nous est pas parvenue)</string>
- <string name="routing_error_not_authorized">Non Autorisé</string>
- <string name="routing_error_pki_failed">Échec de l'envoi chiffré</string>
- <string name="routing_error_pki_send_fail_public_key">Échec de l'envoi de clé privée, pas de clé publique</string>
- <string name="routing_error_pki_unknown_pubkey">Clé publique inconnue</string>
- <string name="routing_error_rate_limit_exceeded">Limite de débit dépassée. Veuillez réessayer plus tard.</string>
<string name="routing_error_timeout">Délai dépassé</string>
- <string name="routing_error_too_large">Paquet trop grand</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Indicateur de force du signal reçu, une mesure utilisée pour déterminer le niveau de puissance reçu par l'antenne. Une valeur RSSI plus élevée indique généralement une connexion plus forte et plus stable.</string>
<string name="rsyslog_server">Serveur Rsyslog</string>

diff --git a/core/resources/src/commonMain/composeResources/values-ga/strings.xml b/core/resources/src/commonMain/composeResources/values-ga/strings.xml
index d39f77a238..4a484e0cf0 100644
--- a/core/resources/src/commonMain/composeResources/values-ga/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-ga/strings.xml
@@ -234,22 +234,10 @@
<string name="role_tak_tracker_desc">Ceadaíonn fadhb beathú do bhoganna PLI i sórtú PLI i feidhm reatha.</string>
<string name="role_tracker_desc">Bíonn sé ag seoladh pacáistí suíomh GPS mar thosaíocht.</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Earráid i eochair sesún an riarthóra</string>
- <string name="routing_error_admin_public_key_unauthorized">Eochair phoiblí riarthóra neamhúdaraithe</string>
- <string name="routing_error_bad_request">Iarratas Mícheart</string>
- <string name="routing_error_duty_cycle_limit">Ceangail cileáil tráth</string>
<string name="routing_error_got_nak">Fáilte atá faighte le haghaidh niúúáil</string>
- <string name="routing_error_max_retransmit">Ceannaire Máx Dúnadh</string>
- <string name="routing_error_no_channel">Gan cainéal</string>
- <string name="routing_error_no_interface">Gan anicéir</string>
- <string name="routing_error_no_response">Gan freagra</string>
<string name="routing_error_no_route">Gan route</string>
<string name="routing_error_none">Faighte</string>
- <string name="routing_error_not_authorized">Gan aithne</string>
- <string name="routing_error_pki_failed">Ní raibh níos saora phósach fadhach</string>
- <string name="routing_error_pki_unknown_pubkey">Pre-set den x-teirí code</string>
<string name="routing_error_timeout">Am tráth</string>
- <string name="routing_error_too_large">Pacáiste ró-mhór</string>
<string name="rssi_definition">Táscaire Cumhachta Athnuachana Aithint an Aoise, tomhas a úsáidtear chun leibhéal cumhachta atá faighte ag an antsnáithe a mheas. Léiríonn RSSI níos airde gnóthachtáil níos laige atá i gceangal seasmhach agus níos láidre.</string>
<!-- SAVE -->
<string name="save">Sábháil</string>

diff --git a/core/resources/src/commonMain/composeResources/values-gl/strings.xml b/core/resources/src/commonMain/composeResources/values-gl/strings.xml
index 8f37bd93f3..0ba13f6d0d 100644
--- a/core/resources/src/commonMain/composeResources/values-gl/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-gl/strings.xml
@@ -195,10 +195,6 @@
<!-- ROLE -->
<string name="role_client_desc">Aplicación conectada ou dispositivo de mensaxería autónomo.</string>
<!-- ROUTING -->
- <string name="routing_error_no_response">Sen resposta</string>
- <string name="routing_error_not_authorized">Non autorizado</string>
- <string name="routing_error_pki_failed">Fallou o envío cifrado</string>
- <string name="routing_error_pki_unknown_pubkey">Chave pública descoñecida</string>
<!-- SAVE -->
<string name="save">Gardar</string>
<string name="save_changes">Gardar</string>

diff --git a/core/resources/src/commonMain/composeResources/values-hr/strings.xml b/core/resources/src/commonMain/composeResources/values-hr/strings.xml
index fbf136194a..38d12d0638 100644
--- a/core/resources/src/commonMain/composeResources/values-hr/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-hr/strings.xml
@@ -200,9 +200,7 @@
<string name="reset_to_defaults">Vrati na početne postavke</string>
<!-- ROLE -->
<!-- ROUTING -->
- <string name="routing_error_no_response">Nema odgovora</string>
<string name="routing_error_none">Potvrđeno</string>
- <string name="routing_error_too_large">Paket je prevelik</string>
<!-- SAVE -->
<string name="save">Spremi</string>
<string name="save_changes">Spremi</string>

diff --git a/core/resources/src/commonMain/composeResources/values-ht/strings.xml b/core/resources/src/commonMain/composeResources/values-ht/strings.xml
index 1b36b8bb14..2605b523ca 100644
--- a/core/resources/src/commonMain/composeResources/values-ht/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-ht/strings.xml
@@ -231,22 +231,10 @@
<string name="role_tak_tracker_desc">Pèmèt emisyon TAK PLI otomatik epi redwi emisyon regilye.</string>
<string name="role_tracker_desc">Voye pakè pozisyon GPS kòm priyorite.</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Kle sesyon move</string>
- <string name="routing_error_admin_public_key_unauthorized">Kle piblik pa otorize</string>
- <string name="routing_error_bad_request">Demann move</string>
- <string name="routing_error_duty_cycle_limit">Limite sik devwa rejyonal rive</string>
<string name="routing_error_got_nak">Rekòmanse avèk yon refi negatif</string>
- <string name="routing_error_max_retransmit">Limite retransmisyon maksimòm rive</string>
- <string name="routing_error_no_channel">Pa gen kanal</string>
- <string name="routing_error_no_interface">Pa gen entèfas</string>
- <string name="routing_error_no_response">Pa gen repons</string>
<string name="routing_error_no_route">Pa gen wout</string>
<string name="routing_error_none">Rekonekte</string>
- <string name="routing_error_not_authorized">Pa otorize</string>
- <string name="routing_error_pki_failed">Echèk voye ankripte</string>
- <string name="routing_error_pki_unknown_pubkey">Kle piblik enkoni</string>
<string name="routing_error_timeout">Tan pase</string>
- <string name="routing_error_too_large">Pake twò gwo</string>
<string name="rssi_definition">Endikatè Fòs Siynal Resevwa, yon mezi ki itilize pou detèmine nivo pouvwa siynal ki resevwa pa antèn nan. Yon RSSI pi wo jeneralman endike yon koneksyon pi fò ak plis estab.</string>
<!-- SAVE -->
<string name="save">Sove</string>

diff --git a/core/resources/src/commonMain/composeResources/values-hu/strings.xml b/core/resources/src/commonMain/composeResources/values-hu/strings.xml
index 4277d0c18f..2422b8022a 100644
--- a/core/resources/src/commonMain/composeResources/values-hu/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-hu/strings.xml
@@ -736,23 +736,10 @@
<string name="root_topic">Gyökér téma</string>
<string name="rotary_encoder_1_enabled">1. forgóenkóder engedélyezve</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Hibás munkamenet kulcs</string>
- <string name="routing_error_admin_public_key_unauthorized">Nem Engedélyezett Publikus Kulcs</string>
- <string name="routing_error_bad_request">Hibás kérés</string>
- <string name="routing_error_duty_cycle_limit">Helyi Üzemciklus Határ Elérve</string>
<string name="routing_error_got_nak">Negatív visszaigazolás érkezett</string>
- <string name="routing_error_max_retransmit">Maximális Újraküldés Elérve</string>
- <string name="routing_error_no_channel">Nincs Csatorna</string>
- <string name="routing_error_no_interface">Nincs Interfész</string>
- <string name="routing_error_no_response">Nincs Válasz</string>
<string name="routing_error_no_route">Nincs út</string>
<string name="routing_error_none">Visszaigazolva</string>
- <string name="routing_error_not_authorized">Nem Engedélyezett</string>
- <string name="routing_error_pki_failed">Titkosított Küldés Sikertelen</string>
- <string name="routing_error_pki_unknown_pubkey">Nem Ismert Publikus Kulcs</string>
- <string name="routing_error_rate_limit_exceeded">Túllépted a sebességkorlátot. Próbáld újra később.</string>
<string name="routing_error_timeout">Időtúllépés</string>
- <string name="routing_error_too_large">Túl nagy csomag</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Vett jelerősség-mutató (RSSI): az antenna által vett jel teljesítményszintjének mérése. A magasabb RSSI általában erősebb, stabilabb kapcsolatot jelez.</string>
<string name="rsyslog_server">rsyslog szerver</string>

diff --git a/core/resources/src/commonMain/composeResources/values-it/strings.xml b/core/resources/src/commonMain/composeResources/values-it/strings.xml
index 9ea09c8495..5624097bd8 100644
--- a/core/resources/src/commonMain/composeResources/values-it/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-it/strings.xml
@@ -1054,7 +1054,6 @@
<string name="message_device_managed">Questa radio è gestita e può essere modificata solo da un amministratore remoto.</string>
<string name="message_input_label">Messaggio</string>
<string name="message_routing_error_max_retransmit">Consegna alla mesh non riuscita</string>
- <string name="message_routing_error_no_channel">Nessun canale selezionato</string>
<string name="message_routing_error_pki_failed">Impossibile inviare il messaggio cifrato</string>
<string name="message_routing_error_pki_send_fail_public_key">Chiave del destinatario non disponibile</string>
<string name="message_routing_error_pki_unknown_pubkey">Il destinatario ha bisogno della tua chiave</string>
@@ -1449,24 +1448,15 @@
<string name="rotary_encoder_1_enabled">Encoder rotativo #1 abilitato</string>
<string name="router_role_confirmation_text">Ho letto la &lt;a href="https://meshtastic.org/docs/configuration/radio/device/#roles"&gt;documentazione sui ruoli del dispositivo&lt;/a&gt; e l'articolo del blog su &lt;a href="http://meshtastic.org/blog/choosing-the-right-device-role"&gt;come scegliere il ruolo giusto per il dispositivo&lt;/a&gt;.</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Chiave di sessione non valida</string>
- <string name="routing_error_admin_public_key_unauthorized">Chiave Pubblica non autorizzata</string>
- <string name="routing_error_bad_request">Richiesta Non Valida</string>
- <string name="routing_error_duty_cycle_limit">Raggiunto il limite del ciclo di lavoro regionale</string>
<string name="routing_error_got_nak">Ricevuta una conferma negativa</string>
- <string name="routing_error_max_retransmit">Tentativi di Ritrasmissione Esauriti</string>
- <string name="routing_error_no_channel">Nessun Canale</string>
- <string name="routing_error_no_interface">Nessuna Interfaccia</string>
- <string name="routing_error_no_response">Nessuna risposta</string>
+ <string name="routing_error_max_retransmit">Consegna alla mesh non riuscita</string>
<string name="routing_error_no_route">Nessun percorso</string>
<string name="routing_error_none">Confermato</string>
- <string name="routing_error_not_authorized">Non Autorizzato</string>
- <string name="routing_error_pki_failed">Invio Cifrato Non Riuscito</string>
- <string name="routing_error_pki_send_fail_public_key">Invio PKI non riuscito, nessuna chiave pubblica</string>
- <string name="routing_error_pki_unknown_pubkey">Chiave Pubblica Sconosciuta</string>
- <string name="routing_error_rate_limit_exceeded">Limite di trasmissione superato. Riprova più tardi.</string>
+ <string name="routing_error_pki_failed">Impossibile inviare il messaggio cifrato</string>
+ <string name="routing_error_pki_send_fail_public_key">Chiave del destinatario non disponibile</string>
+ <string name="routing_error_pki_unknown_pubkey">Il destinatario ha bisogno della tua chiave</string>
<string name="routing_error_timeout">Timeout</string>
- <string name="routing_error_too_large">Pacchetto troppo grande</string>
+ <string name="routing_error_too_large">Il messaggio è troppo grande per essere inviato</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Indicatore di forza del segnale ricevuto (Received Signal Strength Indicator), una misura utilizzata per determinare il livello di potenza ricevuto dall'antenna. Un valore RSSI più elevato indica generalmente una connessione più forte e più stabile.</string>
<string name="rsyslog_server">server rsyslog</string>

diff --git a/core/resources/src/commonMain/composeResources/values-ja/strings.xml b/core/resources/src/commonMain/composeResources/values-ja/strings.xml
index 2c16bcb602..9a9893c705 100644
--- a/core/resources/src/commonMain/composeResources/values-ja/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-ja/strings.xml
@@ -1048,7 +1048,6 @@
<string name="message_device_managed">この無線機は管理されており、リモート管理者のみが変更できます。</string>
<string name="message_input_label">メッセージ</string>
<string name="message_routing_error_max_retransmit">メッシュへの配信に失敗しました</string>
- <string name="message_routing_error_no_channel">チャンネルが選択されていません</string>
<string name="message_routing_error_pki_failed">暗号化メッセージを送信できませんでした</string>
<string name="message_routing_error_pki_send_fail_public_key">受信者の鍵を利用できません</string>
<string name="message_routing_error_pki_unknown_pubkey">受信者にあなたの鍵が必要です</string>
@@ -1443,24 +1442,15 @@
<string name="rotary_encoder_1_enabled">ロータリーエンコーダ #1 を有効化</string>
<string name="router_role_confirmation_text">&lt;a href="https://meshtastic.org/docs/configuration/radio/device/#roles"&gt;デバイスの役割に関するドキュメント&lt;/a&gt;と、&lt;a href="http://meshtastic.org/blog/choosing-the-right-device-role"&gt;適切なデバイスの役割の選び方&lt;/a&gt;に関するブログ記事を読みました。</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">セッション鍵が不正です</string>
- <string name="routing_error_admin_public_key_unauthorized">許可されていない公開鍵</string>
- <string name="routing_error_bad_request">不正な要求</string>
- <string name="routing_error_duty_cycle_limit">リージョンのデューティサイクル上限超過</string>
<string name="routing_error_got_nak">相手が正常に受信できませんでした</string>
- <string name="routing_error_max_retransmit">最大再送信回数に達しました</string>
- <string name="routing_error_no_channel">チャンネルがありません</string>
- <string name="routing_error_no_interface">インターフェースがありません</string>
- <string name="routing_error_no_response">応答なし</string>
+ <string name="routing_error_max_retransmit">メッシュへの配信に失敗しました</string>
<string name="routing_error_no_route">ルートがありません</string>
<string name="routing_error_none">相手の受信を確認しました</string>
- <string name="routing_error_not_authorized">承認されていません</string>
- <string name="routing_error_pki_failed">暗号化された送信に失敗</string>
- <string name="routing_error_pki_send_fail_public_key">PKIの送信に失敗しました。公開鍵がありません</string>
- <string name="routing_error_pki_unknown_pubkey">不明な公開鍵</string>
- <string name="routing_error_rate_limit_exceeded">レート制限を超えました。しばらくしてからもう一度お試しください。</string>
+ <string name="routing_error_pki_failed">暗号化メッセージを送信できませんでした</string>
+ <string name="routing_error_pki_send_fail_public_key">受信者の鍵を利用できません</string>
+ <string name="routing_error_pki_unknown_pubkey">受信者にあなたの鍵が必要です</string>
<string name="routing_error_timeout">タイムアウト</string>
- <string name="routing_error_too_large">パケットが大きすぎます</string>
+ <string name="routing_error_too_large">メッセージが大きすぎて送信できません</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">受信信号強度インジケーター（RSSI）は、アンテナで受信している電力レベルを測定するための指標です。一般的にRSSI値が高いほど、より強力で安定した接続を示します。</string>
<string name="rsyslog_server">rsyslogサーバー</string>

diff --git a/core/resources/src/commonMain/composeResources/values-ko/strings.xml b/core/resources/src/commonMain/composeResources/values-ko/strings.xml
index 38e86c3fc8..96f70a9eab 100644
--- a/core/resources/src/commonMain/composeResources/values-ko/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-ko/strings.xml
@@ -484,22 +484,10 @@
<string name="root_topic">Root topic</string>
<string name="rotary_encoder_1_enabled">로터리 엔코더 #1 활성화</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">세션 키 오류</string>
- <string name="routing_error_admin_public_key_unauthorized">허용되지 않는 공개 키</string>
- <string name="routing_error_bad_request">잘못된 요청</string>
- <string name="routing_error_duty_cycle_limit">Duty Cycle 한도에 도달하였습니다</string>
<string name="routing_error_got_nak">수락 거부됨</string>
- <string name="routing_error_max_retransmit">최대 재 전송 한계에 도달함</string>
- <string name="routing_error_no_channel">채널 없음</string>
- <string name="routing_error_no_interface">인터페이스 없음</string>
- <string name="routing_error_no_response">응답 없음</string>
<string name="routing_error_no_route">루트 없음</string>
<string name="routing_error_none">수락 됨</string>
- <string name="routing_error_not_authorized">승인되지 않음</string>
- <string name="routing_error_pki_failed">암호화 전송 실패</string>
- <string name="routing_error_pki_unknown_pubkey">알 수 없는 공개 키</string>
<string name="routing_error_timeout">시간 초과됨</string>
- <string name="routing_error_too_large">패킷 이 너무 큽니다</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">수신 신호 강도 지표 Received Signal Strength Indicator, RSSI는 안테나가 수신하는 신호의 전력 수준을 측정하는 데 사용되는 지표입니다. RSSI 값이 높을수록 일반적으로 더 강력하고 안정적인 연결을 나타냅니다.</string>
<string name="rsyslog_server">rsyslog 서버</string>

diff --git a/core/resources/src/commonMain/composeResources/values-lt/strings.xml b/core/resources/src/commonMain/composeResources/values-lt/strings.xml
index 09c84fd53b..e8100eab9a 100644
--- a/core/resources/src/commonMain/composeResources/values-lt/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-lt/strings.xml
@@ -239,22 +239,10 @@
<string name="role_tak_tracker_desc">Įgalina automatines TAK PLI transliacijas ir sumažina rutininių transliacijų kiekį.</string>
<string name="role_tracker_desc">Pirmenybinis GPS pozicijos paketų siuntimas</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Blogas sesijos raktas</string>
- <string name="routing_error_admin_public_key_unauthorized">Viešasis raktas nepatvirtintas</string>
- <string name="routing_error_bad_request">Bloga užklausa</string>
- <string name="routing_error_duty_cycle_limit">Pasiektas regioninis ciklų limitas</string>
<string name="routing_error_got_nak">Gautas negatyvus patvirtinimas</string>
- <string name="routing_error_max_retransmit">Pasiektas persiuntimų limitas</string>
- <string name="routing_error_no_channel">Nėra kanalo</string>
- <string name="routing_error_no_interface">Nėra sąsajos</string>
- <string name="routing_error_no_response">Nėra atsakymo</string>
<string name="routing_error_no_route">Nėra maršruto</string>
<string name="routing_error_none">Pristatymas patvirtintas</string>
- <string name="routing_error_not_authorized">Neautorizuotas</string>
- <string name="routing_error_pki_failed">Šifruotas siuntimas nepavyko</string>
- <string name="routing_error_pki_unknown_pubkey">Nežinomas viešasis raktas</string>
<string name="routing_error_timeout">Baigėsi laikas</string>
- <string name="routing_error_too_large">Paketas perdidelis</string>
<string name="rssi">RSSI</string>
<!-- SAVE -->
<string name="save">Išsaugoti</string>

diff --git a/core/resources/src/commonMain/composeResources/values-nl/strings.xml b/core/resources/src/commonMain/composeResources/values-nl/strings.xml
index 20122c644e..c24281ebe3 100644
--- a/core/resources/src/commonMain/composeResources/values-nl/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-nl/strings.xml
@@ -384,22 +384,10 @@
<string name="role_tak_tracker_desc">Activeer automatisch zenden TAK PLI en beperk routine zendingen.</string>
<string name="role_tracker_desc">Zendt GPS-positiepakketten met prioriteit uit.</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Ongeldige sessiesleutel</string>
- <string name="routing_error_admin_public_key_unauthorized">Publieke sleutel onbevoegd</string>
- <string name="routing_error_bad_request">Ongeldige aanvraag</string>
- <string name="routing_error_duty_cycle_limit">Regionale limiet inschakeltijd bereikt</string>
<string name="routing_error_got_nak">Negatieve bevestiging ontvangen</string>
- <string name="routing_error_max_retransmit">Maximum Pogingen Bereikt</string>
- <string name="routing_error_no_channel">Geen Kanaal</string>
- <string name="routing_error_no_interface">Geen Interface</string>
- <string name="routing_error_no_response">Geen antwoord</string>
<string name="routing_error_no_route">Geen route</string>
<string name="routing_error_none">Bevestigd</string>
- <string name="routing_error_not_authorized">Niet Bevoegd</string>
- <string name="routing_error_pki_failed">Versleuteld verzenden mislukt</string>
- <string name="routing_error_pki_unknown_pubkey">Onbekende publieke sleutel</string>
<string name="routing_error_timeout">Time-Out</string>
- <string name="routing_error_too_large">Pakket te groot</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Ontvangen Signal Sterkte Indicator, een meting gebruikt om het stroomniveau te bepalen dat de antenne ontvangt. Een hogere RSSI-waarde geeft een sterkere en stabielere verbinding aan.</string>
<string name="rsyslog_server">rsyslog server</string>

diff --git a/core/resources/src/commonMain/composeResources/values-no/strings.xml b/core/resources/src/commonMain/composeResources/values-no/strings.xml
index ab53e7f570..62c8f05135 100644
--- a/core/resources/src/commonMain/composeResources/values-no/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-no/strings.xml
@@ -243,22 +243,10 @@
<string name="role_tak_tracker_desc">Aktiverer automatiske TAK PLI-sendinger og reduserer rutinesendinger.</string>
<string name="role_tracker_desc">Sender GPS-posisjonspakker som prioritert.</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Ikke-gyldig sesjonsnøkkel</string>
- <string name="routing_error_admin_public_key_unauthorized">Ikke-autorisert offentlig nøkkel</string>
- <string name="routing_error_bad_request">Ugyldig Forespørsel</string>
- <string name="routing_error_duty_cycle_limit">Regional Arbeidssyklusgrense Nådd</string>
<string name="routing_error_got_nak">Mottok negativ bekreftelse</string>
- <string name="routing_error_max_retransmit">Maks Retransmisjoner Nådd</string>
- <string name="routing_error_no_channel">Ingen Kanal</string>
- <string name="routing_error_no_interface">Ingen grensesnitt</string>
- <string name="routing_error_no_response">Ingen respons</string>
<string name="routing_error_no_route">Ingen rute</string>
<string name="routing_error_none">Bekreftet</string>
- <string name="routing_error_not_authorized">Ikke Autorisert</string>
- <string name="routing_error_pki_failed">Kryptert sending mislyktes</string>
- <string name="routing_error_pki_unknown_pubkey">Ukjent Offentlig Nøkkel</string>
<string name="routing_error_timeout">Tidsavbrudd</string>
- <string name="routing_error_too_large">Pakken er for stor</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">"Received Signal Strength Indicator", en måling som brukes til å bestemme strømnivået som mottas av antennen. Høyere RSSI verdi indikerer generelt en sterkere og mer stabil forbindelse.</string>
<!-- SAVE -->

diff --git a/core/resources/src/commonMain/composeResources/values-pl/strings.xml b/core/resources/src/commonMain/composeResources/values-pl/strings.xml
index ef00442e59..a132923955 100644
--- a/core/resources/src/commonMain/composeResources/values-pl/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-pl/strings.xml
@@ -680,23 +680,10 @@
<string name="role_tracker_desc">Tracker - Do użytku z urządzeniami przeznaczonymi jako śledzenie GPS. Pakiety pozycyjne wysyłane z tego urządzenia będą miały wyższy priorytet, z nadawaniem pozycji co dwie minuty. Inteligentna transmisja pozycji będzie domyślnie wyłączona.</string>
<string name="root_topic">Główny temat</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Nieprawidłowy klucz sesji</string>
- <string name="routing_error_admin_public_key_unauthorized">Nieautoryzowany klucz publiczny</string>
- <string name="routing_error_bad_request">Błędne żądanie</string>
- <string name="routing_error_duty_cycle_limit">Osiągnięto okresowy limit nadawania dla tego regionu</string>
<string name="routing_error_got_nak">Otrzymano negatywne potwierdzenie</string>
- <string name="routing_error_max_retransmit">Przekroczono czas lub liczbę retransmisji</string>
- <string name="routing_error_no_channel">Brak kanału</string>
- <string name="routing_error_no_interface">Brak interfejsu</string>
- <string name="routing_error_no_response">Brak odpowiedzi</string>
<string name="routing_error_no_route">Brak trasy</string>
<string name="routing_error_none">Potwierdzone</string>
- <string name="routing_error_not_authorized">Brak autoryzacji</string>
- <string name="routing_error_pki_failed">Zaszyfrowane wysyłanie nie powiodło się</string>
- <string name="routing_error_pki_send_fail_public_key">Nie wysłano PKI, brak klucza publicznego</string>
- <string name="routing_error_pki_unknown_pubkey">Nieznany klucz publiczny</string>
<string name="routing_error_timeout">Upłynął limit czasu</string>
- <string name="routing_error_too_large">Pakiet jest zbyt duży</string>
<string name="rssi">RSSI:</string>
<string name="rssi_definition">Received Signal Strength Indicator - miara używana do określenia poziomu mocy odbieranej przez antenę. Wyższa wartość RSSI zazwyczaj oznacza silniejsze i bardziej stabilne połączenie.</string>
<string name="rsyslog_server">Serwer rsyslog</string>

diff --git a/core/resources/src/commonMain/composeResources/values-pt-rBR/strings.xml b/core/resources/src/commonMain/composeResources/values-pt-rBR/strings.xml
index 89af8c632e..5decd47dd1 100644
--- a/core/resources/src/commonMain/composeResources/values-pt-rBR/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-pt-rBR/strings.xml
@@ -616,23 +616,10 @@
<string name="root_topic">Tópico principal</string>
<string name="rotary_encoder_1_enabled">Codificador rotativo #1 ativado</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Chave de sessão incorreta</string>
- <string name="routing_error_admin_public_key_unauthorized">Chave Publica não autorizada</string>
- <string name="routing_error_bad_request">Requisição Inválida</string>
- <string name="routing_error_duty_cycle_limit">Limite Regional de Ciclo de Trabalho Alcançado</string>
<string name="routing_error_got_nak">Recebi uma negativa de reconhecimento</string>
- <string name="routing_error_max_retransmit">Limite de Retransmissões Atingido</string>
- <string name="routing_error_no_channel">Nenhum canal</string>
- <string name="routing_error_no_interface">Sem interface</string>
- <string name="routing_error_no_response">Nenhuma resposta</string>
<string name="routing_error_no_route">Sem rota</string>
<string name="routing_error_none">Reconhecido</string>
- <string name="routing_error_not_authorized">Não Autorizado</string>
- <string name="routing_error_pki_failed">Falha de Envio Criptografado</string>
- <string name="routing_error_pki_unknown_pubkey">Chave Pública Desconhecida</string>
- <string name="routing_error_rate_limit_exceeded">Limite excedido. Por favor, tente novamente mais tarde.</string>
<string name="routing_error_timeout">Tempo esgotado</string>
- <string name="routing_error_too_large">Pacote grande demais</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Indicador de Força de Sinal Recebido, uma medida usada para determinar o nível de potência que está sendo recebida pela antena. Um valor maior de RSSI geralmente indica uma conexão mais forte e mais estável.</string>
<string name="rsyslog_server">Servidor rsyslog</string>

diff --git a/core/resources/src/commonMain/composeResources/values-pt/strings.xml b/core/resources/src/commonMain/composeResources/values-pt/strings.xml
index 5dd7ad49cd..379667cc98 100644
--- a/core/resources/src/commonMain/composeResources/values-pt/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-pt/strings.xml
@@ -469,22 +469,10 @@
<string name="root_topic">Tópico principal</string>
<string name="rotary_encoder_1_enabled">Ativar Codificador rotativo #1</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Chave de sessão inválida</string>
- <string name="routing_error_admin_public_key_unauthorized">Public Key não autorizada</string>
- <string name="routing_error_bad_request">Pedido Inválido</string>
- <string name="routing_error_duty_cycle_limit">Limite do Duty Cycle Regional Atingido</string>
<string name="routing_error_got_nak">Recebida uma confirmação negativa</string>
- <string name="routing_error_max_retransmit">Máximo de Retransmissão Atingido</string>
- <string name="routing_error_no_channel">Sem canal</string>
- <string name="routing_error_no_interface">Sem interface</string>
- <string name="routing_error_no_response">Sem resposta</string>
<string name="routing_error_no_route">Sem rota</string>
<string name="routing_error_none">Confirmar</string>
- <string name="routing_error_not_authorized">Não Autorizado</string>
- <string name="routing_error_pki_failed">Envio cifrado falhou</string>
- <string name="routing_error_pki_unknown_pubkey">Chave pública desconhecida</string>
<string name="routing_error_timeout">Timeout</string>
- <string name="routing_error_too_large">Pacote demasiado grande</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Indicador de Força de Sinal Recebido, uma medida usada para determinar o nível de energia que está a ser recebido pela antena. Um valor mais elevado de RSSI geralmente indica uma conexão mais forte e mais estável.</string>
<string name="rsyslog_server">servidor rsyslog</string>

diff --git a/core/resources/src/commonMain/composeResources/values-ro/strings.xml b/core/resources/src/commonMain/composeResources/values-ro/strings.xml
index 0b309fb227..67e1ebec5a 100644
--- a/core/resources/src/commonMain/composeResources/values-ro/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-ro/strings.xml
@@ -946,24 +946,10 @@
<string name="root_topic">Temă rădăcină</string>
<string name="rotary_encoder_1_enabled">Encoder rotativ #1 activat</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Cheie de sesiune incorectă</string>
- <string name="routing_error_admin_public_key_unauthorized">Cheie publică neautorizată</string>
- <string name="routing_error_bad_request">Solicitare invalidă</string>
- <string name="routing_error_duty_cycle_limit">Limita regională a ciclului de funcționare atinsă</string>
<string name="routing_error_got_nak">S-a primit o confirmare negativă</string>
- <string name="routing_error_max_retransmit">Retransmisie maximă atinsă</string>
- <string name="routing_error_no_channel">Niciun canal</string>
- <string name="routing_error_no_interface">Fără interfață</string>
- <string name="routing_error_no_response">Nici un răspuns</string>
<string name="routing_error_no_route">Nici o rută</string>
<string name="routing_error_none">Confirmat</string>
- <string name="routing_error_not_authorized">Neautorizat</string>
- <string name="routing_error_pki_failed">Trimitere criptată nereușită</string>
- <string name="routing_error_pki_send_fail_public_key">Trimiterea PKI nu a reușit, nici o cheie publică</string>
- <string name="routing_error_pki_unknown_pubkey">Cheie publică necunoscută</string>
- <string name="routing_error_rate_limit_exceeded">Rata limită depășită. Te rugăm să încerci din nou mai târziu.</string>
<string name="routing_error_timeout">Expirat</string>
- <string name="routing_error_too_large">Pachet prea mare</string>
<string name="rssi"> RSSI</string>
<string name="rssi_definition">Indicatorul intensității semnalului recepționat (Received Signal Strength Indicator), o măsurătoare utilizată pentru a determina nivelul de putere recepționat de antenă. O valoare RSSI mai mare indică, în general, o conexiune mai puternică și mai stabilă.</string>
<string name="rsyslog_server">server rsyslog</string>

diff --git a/core/resources/src/commonMain/composeResources/values-ru/strings.xml b/core/resources/src/commonMain/composeResources/values-ru/strings.xml
index df7eb428a9..f0ad23ddf7 100644
--- a/core/resources/src/commonMain/composeResources/values-ru/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-ru/strings.xml
@@ -1066,7 +1066,6 @@
<string name="message_device_managed">Это радио управляется и может быть изменено только удаленным администратором.</string>
<string name="message_input_label">Сообщение</string>
<string name="message_routing_error_max_retransmit">Не удалось доставить в сеть</string>
- <string name="message_routing_error_no_channel">Канал не выбран</string>
<string name="message_routing_error_pki_failed">Не удалось отправить зашифрованное сообщение</string>
<string name="message_routing_error_pki_send_fail_public_key">Ключ получателя недоступен</string>
<string name="message_routing_error_pki_unknown_pubkey">Получателю нужен ваш ключ</string>
@@ -1473,24 +1472,15 @@
<string name="rotary_encoder_1_enabled">Поворотный энкодер #1 включен</string>
<string name="router_role_confirmation_text">Я прочитал &lt;a href="https://meshtastic.org/docs/configuration/radio/device/#roles"&gt;Документацию по роли устройств&lt;/a&gt; и пост в блоге о &lt;a href="http://meshtastic.org/blog/choosing-the-right-device-role"&gt;Выборе верной роли устройства&lt;/a&gt;.</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Неверный ключ сессии</string>
- <string name="routing_error_admin_public_key_unauthorized">Публичный ключ не авторизован</string>
- <string name="routing_error_bad_request">Неверный запрос</string>
- <string name="routing_error_duty_cycle_limit">Достигнут региональный предел рабочего цикла</string>
<string name="routing_error_got_nak">Получено отрицательное подтверждение</string>
- <string name="routing_error_max_retransmit">Достигнут лимит ретрансляции</string>
- <string name="routing_error_no_channel">Нет канала</string>
- <string name="routing_error_no_interface">Нет интерфейса</string>
- <string name="routing_error_no_response">Нет ответа</string>
+ <string name="routing_error_max_retransmit">Не удалось доставить в сеть</string>
<string name="routing_error_no_route">Нет маршрута</string>
<string name="routing_error_none">Принято</string>
- <string name="routing_error_not_authorized">Не авторизован</string>
- <string name="routing_error_pki_failed">Ошибка шифрования отправки</string>
- <string name="routing_error_pki_send_fail_public_key">PKI не отправлен, нет открытого ключа</string>
- <string name="routing_error_pki_unknown_pubkey">Неизвестный публичный ключ</string>
- <string name="routing_error_rate_limit_exceeded">Превышен лимит запросов. Пожалуйста, повторите попытку позже.</string>
+ <string name="routing_error_pki_failed">Не удалось отправить зашифрованное сообщение</string>
+ <string name="routing_error_pki_send_fail_public_key">Ключ получателя недоступен</string>
+ <string name="routing_error_pki_unknown_pubkey">Получателю нужен ваш ключ</string>
<string name="routing_error_timeout">Время ожидания истекло</string>
- <string name="routing_error_too_large">Пакет слишком велик</string>
+ <string name="routing_error_too_large">Слишком большое сообщение для отправки</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Индикатор уровня принимаемого сигнала, измерение, используемое для определения уровня мощности, принимаемой антенной. Более высокое значение RSSI обычно указывает на более сильное и стабильное соединение.</string>
<string name="rsyslog_server">Сервер rsyslog</string>

diff --git a/core/resources/src/commonMain/composeResources/values-sk/strings.xml b/core/resources/src/commonMain/composeResources/values-sk/strings.xml
index 5cb66fdc09..72c95c2bee 100644
--- a/core/resources/src/commonMain/composeResources/values-sk/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-sk/strings.xml
@@ -407,22 +407,10 @@
<string name="role_tracker_desc">Prioritne vysiela pakety polohy GPS.</string>
<string name="rotary_encoder_1_enabled">Enkóder #1 aktivovaný</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Zlý kľúč relácie</string>
- <string name="routing_error_admin_public_key_unauthorized">Verejný kľúč neautorizovaný</string>
- <string name="routing_error_bad_request">Nesprávna požiadavka</string>
- <string name="routing_error_duty_cycle_limit">Dosiahnutý regionálny limit pracovného cyklu</string>
<string name="routing_error_got_nak">Prijaté negatívne potvrdenie</string>
- <string name="routing_error_max_retransmit">Dosiahnutý maximum opakovaných prenosov</string>
- <string name="routing_error_no_channel">Žiaden kanál</string>
- <string name="routing_error_no_interface">Žiadne rozhranie</string>
- <string name="routing_error_no_response">Bez odozvy</string>
<string name="routing_error_no_route">Žiadna trasa</string>
<string name="routing_error_none">Potvrdené</string>
- <string name="routing_error_not_authorized">Neautorizované</string>
- <string name="routing_error_pki_failed">Zlyhalo šifrované odosielanie</string>
- <string name="routing_error_pki_unknown_pubkey">Neznámy verejný kľúč</string>
<string name="routing_error_timeout">Časový limit</string>
- <string name="routing_error_too_large">Príliš veľký paket</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Indikátor sily prijímaného signálu (RSSI), meranie používané na určenie úrovne výkonu prijatého skrz anténu. Vyššia hodnota RSSI vo všeobecnosti znamená silnejšie a stabilnejšie pripojenie.</string>
<!-- SAVE -->

diff --git a/core/resources/src/commonMain/composeResources/values-sl/strings.xml b/core/resources/src/commonMain/composeResources/values-sl/strings.xml
index ec7e7c20a6..ae04dbfb86 100644
--- a/core/resources/src/commonMain/composeResources/values-sl/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-sl/strings.xml
@@ -245,22 +245,10 @@
<string name="role_tak_tracker_desc">Omogoča samodejno oddajanje TAK PLI in zmanjšuje rutinsko oddajanje.</string>
<string name="role_tracker_desc">Prednostno oddaja paketke GPS položaja.</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Napačen sejni ključ</string>
- <string name="routing_error_admin_public_key_unauthorized">Javni ključ ni pooblaščen</string>
- <string name="routing_error_bad_request">Slaba zahteva</string>
- <string name="routing_error_duty_cycle_limit">Dosežena regionalna omejitev delovnega cikla</string>
<string name="routing_error_got_nak">Prejeta negativna potrditev</string>
- <string name="routing_error_max_retransmit">Dosežena meja ponovnega pošiljanja</string>
- <string name="routing_error_no_channel">Brez kanala</string>
- <string name="routing_error_no_interface">Brez vmesnika</string>
- <string name="routing_error_no_response">Brez odgovora</string>
<string name="routing_error_no_route">Brez poti</string>
<string name="routing_error_none">Potrjeno</string>
- <string name="routing_error_not_authorized">Niste pooblaščeni</string>
- <string name="routing_error_pki_failed">Šifrirano pošiljanje ni uspelo</string>
- <string name="routing_error_pki_unknown_pubkey">Neznan javni ključ</string>
<string name="routing_error_timeout">Časovna omejitev</string>
- <string name="routing_error_too_large">Paketek je prevelik</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Indikator moči sprejetega signala je meritev, ki se uporablja za določanje ravni moči, ki jo sprejema antena. Višja vrednost RSSI na splošno pomeni močnejšo in stabilnejšo povezavo.</string>
<!-- SAVE -->

diff --git a/core/resources/src/commonMain/composeResources/values-sq/strings.xml b/core/resources/src/commonMain/composeResources/values-sq/strings.xml
index fe4f4c5c23..d4a588c9c3 100644
--- a/core/resources/src/commonMain/composeResources/values-sq/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-sq/strings.xml
@@ -238,22 +238,10 @@
<string name="role_tak_tracker_desc">Aktivizon transmetimet automatikisht TAK PLI dhe zvogëlon transmetimet rutinë.</string>
<string name="role_tracker_desc">Transmeton paketa pozicioni GPS si prioritet.</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Çelës sesioni i gabuar</string>
- <string name="routing_error_admin_public_key_unauthorized">Çelësi publik i paautorizuar</string>
- <string name="routing_error_bad_request">Kërkesë e gabuar</string>
- <string name="routing_error_duty_cycle_limit">Arritur kufiri i ciklit të detyrës rajonale</string>
<string name="routing_error_got_nak">Marrë një njohje negative</string>
- <string name="routing_error_max_retransmit">Arritur kufiri i ri-dërgimeve</string>
- <string name="routing_error_no_channel">Nuk ka kanal</string>
- <string name="routing_error_no_interface">Nuk ka ndërfaqe</string>
- <string name="routing_error_no_response">Nuk ka përgjigje</string>
<string name="routing_error_no_route">Nuk ka rrugë</string>
<string name="routing_error_none">Pranuar</string>
- <string name="routing_error_not_authorized">Nuk jeni të autorizuar</string>
- <string name="routing_error_pki_failed">Dërgesa e enkriptuar ka dështuar</string>
- <string name="routing_error_pki_unknown_pubkey">Çelësi publik i panjohur</string>
<string name="routing_error_timeout">Koha e skaduar</string>
- <string name="routing_error_too_large">Paketa shumë e madhe</string>
<string name="rssi_definition">Indikatori i Fuqisë së Sinjalit të Marrë, një matje e përdorur për të përcaktuar nivelin e energjisë që po merret nga antena. Një vlerë më e lartë RSSI zakonisht tregon një lidhje më të fortë dhe më të qëndrueshme.</string>
<!-- SAVE -->
<string name="save">Ruaj</string>

diff --git a/core/resources/src/commonMain/composeResources/values-sr/strings.xml b/core/resources/src/commonMain/composeResources/values-sr/strings.xml
index 08460c95ab..a028279700 100644
--- a/core/resources/src/commonMain/composeResources/values-sr/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-sr/strings.xml
@@ -416,22 +416,10 @@
<string name="role_tak_tracker_desc">Omogućava autmatske TAK PLI emisije i smanjuje rutinske emisije.</string>
<string name="role_tracker_desc">Emituje GPS pakete položaja kao prioritet.</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Loš ključ sesije</string>
- <string name="routing_error_admin_public_key_unauthorized">Javni ključ nije autorizovan</string>
- <string name="routing_error_bad_request">Loš zahtev</string>
- <string name="routing_error_duty_cycle_limit">Dostignut regionalni limit ciklusa rada</string>
<string name="routing_error_got_nak">Primljena negativna potvrda</string>
- <string name="routing_error_max_retransmit">Dostignut maksimalni broj ponovnih slanja</string>
- <string name="routing_error_no_channel">Nema kanala</string>
- <string name="routing_error_no_interface">Nema interfejsa</string>
- <string name="routing_error_no_response">Nema odgovora</string>
<string name="routing_error_no_route">Nema rute</string>
<string name="routing_error_none">Potvrđeno</string>
- <string name="routing_error_not_authorized">Bez ovlašćenja</string>
- <string name="routing_error_pki_failed">Šifrovani prenos nije uspeo</string>
- <string name="routing_error_pki_unknown_pubkey">Nepoznat javni ključ</string>
<string name="routing_error_timeout">Isteklo vreme</string>
- <string name="routing_error_too_large">Paket prevelik</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Indikator jačine primljenog signala RSSI, merenje koje se koristi za određivanje nivoa snage koji antena prima. Viša vrednost RSSI generalno ukazuje na jaču i stabilniju vezu.</string>
<string name="sats">Сателита</string>

diff --git a/core/resources/src/commonMain/composeResources/values-srp/strings.xml b/core/resources/src/commonMain/composeResources/values-srp/strings.xml
index 4d12729685..f92121b19f 100644
--- a/core/resources/src/commonMain/composeResources/values-srp/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-srp/strings.xml
@@ -416,22 +416,10 @@
<string name="role_tak_tracker_desc">Омогућава аутоматске TAK PLI емисије и смањује рутинске емисије.</string>
<string name="role_tracker_desc">Емитује пакете са GPS позицијом као приоритет.</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Лош кључ сесије</string>
- <string name="routing_error_admin_public_key_unauthorized">Јавни кључ није ауторизован</string>
- <string name="routing_error_bad_request">Лош захтев</string>
- <string name="routing_error_duty_cycle_limit">Достигнут регионални лимит циклуса рада</string>
<string name="routing_error_got_nak">Примљена негативна потврда</string>
- <string name="routing_error_max_retransmit">Достигнут максимални број поновних слања</string>
- <string name="routing_error_no_channel">Нема канала</string>
- <string name="routing_error_no_interface">Нема интерфејса</string>
- <string name="routing_error_no_response">Нема одговора</string>
<string name="routing_error_no_route">Нема руте</string>
<string name="routing_error_none">Потврђено</string>
- <string name="routing_error_not_authorized">Без овлашћења</string>
- <string name="routing_error_pki_failed">Шифровани пренос није успео</string>
- <string name="routing_error_pki_unknown_pubkey">Непознат јавни кључ</string>
<string name="routing_error_timeout">Истекло време</string>
- <string name="routing_error_too_large">Пакет превелик</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Индикатор јачине примљеног сигнала RSSI је мера која се користи за одређивање нивоа снаге која се прима преко антене. Виша вредност RSSI генерално указује на јачу и стабилнију везу.</string>
<string name="sats">Сателита</string>

diff --git a/core/resources/src/commonMain/composeResources/values-sv/strings.xml b/core/resources/src/commonMain/composeResources/values-sv/strings.xml
index 7252e5fb88..b2eb4fbabd 100644
--- a/core/resources/src/commonMain/composeResources/values-sv/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-sv/strings.xml
@@ -1085,24 +1085,10 @@
<string name="role_tracker_desc">Nod som prioriterar GPS meddelanden.</string>
<string name="root_topic">Rotämne (root topic)</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Felaktig sessionsnyckel</string>
- <string name="routing_error_admin_public_key_unauthorized">Obehörig publik nyckel</string>
- <string name="routing_error_bad_request">Misslyckad</string>
- <string name="routing_error_duty_cycle_limit">Gränsen för intermittensfaktor uppnådd</string>
<string name="routing_error_got_nak">Misslyckad kvittens</string>
- <string name="routing_error_max_retransmit">Maximalt antal sändningar nådd</string>
- <string name="routing_error_no_channel">Ingen kanal</string>
- <string name="routing_error_no_interface">Inget gränssnitt</string>
- <string name="routing_error_no_response">Inget svar</string>
<string name="routing_error_no_route">Ingen rutt</string>
<string name="routing_error_none">Kvitterad</string>
- <string name="routing_error_not_authorized">Ej behörig</string>
- <string name="routing_error_pki_failed">Krypterad sändning misslyckades</string>
- <string name="routing_error_pki_send_fail_public_key">PKI-sändningen misslyckades, ingen offentlig nyckel</string>
- <string name="routing_error_pki_unknown_pubkey">Okänd publik nyckel</string>
- <string name="routing_error_rate_limit_exceeded">Sändningsgräns uppnådd. Försök igen senare.</string>
<string name="routing_error_timeout">Timeout</string>
- <string name="routing_error_too_large">Paket för stort</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Received Signal Strength Indicator, ett mått som används för att avgöra effektnivån som togs emot av antennen. Ett högre RSSI-värde indikerar generellt en starkare och stabilare anslutning.</string>
<string name="rsyslog_server">rsyslog-server</string>

diff --git a/core/resources/src/commonMain/composeResources/values-tr/strings.xml b/core/resources/src/commonMain/composeResources/values-tr/strings.xml
index 4b979565dc..23deccbe76 100644
--- a/core/resources/src/commonMain/composeResources/values-tr/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-tr/strings.xml
@@ -496,22 +496,10 @@
<string name="root_topic">Ana konu</string>
<string name="rotary_encoder_1_enabled">Dönen kodlayıcı #1 etkinleştirildi</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Hatalı oturum anahtarı</string>
- <string name="routing_error_admin_public_key_unauthorized">Genel Anahtar yetkisiz</string>
- <string name="routing_error_bad_request">Geçersiz İstek</string>
- <string name="routing_error_duty_cycle_limit">Bölgesel Görev Çevrimi Limitine Ulaşıldı</string>
<string name="routing_error_got_nak">Negatif bir onay alındı</string>
- <string name="routing_error_max_retransmit">Azami Yeniden Gönderme Limitine Ulaşıldı</string>
- <string name="routing_error_no_channel">Kanal yok</string>
- <string name="routing_error_no_interface">Arayüz Yok</string>
- <string name="routing_error_no_response">Yanıt yok</string>
<string name="routing_error_no_route">Rota yok</string>
<string name="routing_error_none">Onaylandı</string>
- <string name="routing_error_not_authorized">Yetkisiz</string>
- <string name="routing_error_pki_failed">Şifreli Gönderme Başarısız</string>
- <string name="routing_error_pki_unknown_pubkey">Bilinmeyen Genel Anahtar</string>
<string name="routing_error_timeout">Zaman Aşımı</string>
- <string name="routing_error_too_large">Paket çok büyük</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Alınan Sinyal Gücü Göstergesi, anten tarafından alınan güç seviyesini belirlemek için kullanılan bir ölçüdür. Daha yüksek bir RSSI değeri genellikle daha güçlü ve daha istikrarlı bir bağlantıya işaret eder.</string>
<string name="rsyslog_server">rsyslog sunucusu</string>

diff --git a/core/resources/src/commonMain/composeResources/values-uk/strings.xml b/core/resources/src/commonMain/composeResources/values-uk/strings.xml
index da2cd43dce..3e0118ff55 100644
--- a/core/resources/src/commonMain/composeResources/values-uk/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-uk/strings.xml
@@ -1075,24 +1075,10 @@
<string name="rotary_encoder_1_enabled">Енкодер #1 активований</string>
<string name="router_role_confirmation_text">Я прочитав(-ла) &lt;a href="https://meshtastic.org/docs/configuration/radio/device/#roles"&gt;Device Role Documentation&lt;/a&gt; і допис у блозі про &lt;a href="http://meshtastic.org/blog/choosing-the-right-device-role"&gt;Choosing The Right Device Role&lt;/a&gt;.</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">Помилка ключа сеансу</string>
- <string name="routing_error_admin_public_key_unauthorized">Несанкціонований відкритий ключ</string>
- <string name="routing_error_bad_request">Невірний запит</string>
- <string name="routing_error_duty_cycle_limit">Перевищено регіональний ліміт ефіру</string>
<string name="routing_error_got_nak">Отримано негативне підтвердження</string>
- <string name="routing_error_max_retransmit">Досягнуто ліміт спроб</string>
- <string name="routing_error_no_channel">Канал відсутній</string>
- <string name="routing_error_no_interface">Інтерфейс відсутній</string>
- <string name="routing_error_no_response">Немає відповіді</string>
<string name="routing_error_no_route">Маршрут відсутній</string>
<string name="routing_error_none">Підтверджено</string>
- <string name="routing_error_not_authorized">Не авторизований</string>
- <string name="routing_error_pki_failed">Помилка зашифрованої передачі</string>
- <string name="routing_error_pki_send_fail_public_key">Помилка надсилання PKI, відсутній публічний ключ</string>
- <string name="routing_error_pki_unknown_pubkey">Невідомий відкритий ключ</string>
- <string name="routing_error_rate_limit_exceeded">Перевищено ліміт запитів. Будь ласка, спробуйте пізніше.</string>
<string name="routing_error_timeout">Таймаут</string>
- <string name="routing_error_too_large">Пакет завеликий</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">Показник рівня потужності сигналу — вимірювання, що використовується для визначення рівня потужності, що приймається антеною. Вище значення RSSI зазвичай вказує на міцніше та стабільніше з'єднання.</string>
<string name="rsyslog_server">rsyslog-сервер</string>

diff --git a/core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml b/core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml
index d28c81aa95..396eeb324e 100644
--- a/core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml
@@ -1060,7 +1060,6 @@
<string name="message_device_managed">此电台由远程管理员管理。</string>
<string name="message_input_label">信息</string>
<string name="message_routing_error_max_retransmit">发送至MESH失败</string>
- <string name="message_routing_error_no_channel">未选择信道</string>
<string name="message_routing_error_pki_failed">无法发送加密消息</string>
<string name="message_routing_error_pki_send_fail_public_key">接收方密钥不可用</string>
<string name="message_routing_error_pki_unknown_pubkey">接收方需要你的密钥</string>
@@ -1455,24 +1454,15 @@
<string name="rotary_encoder_1_enabled">启用旋转编码器 #1 </string>
<string name="router_role_confirmation_text">我已经阅读了 &lt;a href="https://meshtastic.org/docs/configuration/radio/device/#roles"&gt;设备角色文档&lt;/a&gt; 这篇博客文章&lt;a href="http://meshtastic.org/blog/choosing-the-right-device-role"&gt;选择合适的设备角色&lt;/a&gt;。</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">会话密钥错误</string>
- <string name="routing_error_admin_public_key_unauthorized">未授权的公钥</string>
- <string name="routing_error_bad_request">错误请求</string>
- <string name="routing_error_duty_cycle_limit">区域占空比限制已达到</string>
<string name="routing_error_got_nak">接收到否定确认</string>
- <string name="routing_error_max_retransmit">已达到最大再传输量</string>
- <string name="routing_error_no_channel">无频道</string>
- <string name="routing_error_no_interface">无界面</string>
- <string name="routing_error_no_response">无响应</string>
+ <string name="routing_error_max_retransmit">发送至MESH失败</string>
<string name="routing_error_no_route">无路径</string>
<string name="routing_error_none">已确认</string>
- <string name="routing_error_not_authorized">未授权</string>
- <string name="routing_error_pki_failed">加密发送失败！</string>
- <string name="routing_error_pki_send_fail_public_key">PKI 发送失败，无公钥</string>
- <string name="routing_error_pki_unknown_pubkey">未知公钥</string>
- <string name="routing_error_rate_limit_exceeded">超过速率限制。请稍后再试。</string>
+ <string name="routing_error_pki_failed">无法发送加密消息</string>
+ <string name="routing_error_pki_send_fail_public_key">接收方密钥不可用</string>
+ <string name="routing_error_pki_unknown_pubkey">接收方需要你的密钥</string>
<string name="routing_error_timeout">超时</string>
- <string name="routing_error_too_large">数据包过大</string>
+ <string name="routing_error_too_large">消息太大，无法发送</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">接收信号强度指示（Received Signal Strength Indicator, RSSI）是一种用于测量天线接收到的信号功率的指标。较高的 RSSI 值通常表示更强、更稳定的连接。</string>
<string name="rsyslog_server">rsyslog 服务器</string>

diff --git a/core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml b/core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml
index e9b3ec61e1..1cdb9eb9f9 100644
--- a/core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml
+++ b/core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml
@@ -1119,24 +1119,10 @@
<string name="rotary_encoder_1_enabled">啟用旋轉編碼器#1</string>
<string name="router_role_confirmation_text">我已閱讀&lt;a href="https://meshtastic.org/docs/configuration/radio/device/#roles"&gt;裝置角色說明文件&lt;/a&gt;以及關於&lt;a href="http://meshtastic.org/blog/choosing-the-right-device-role"&gt;選擇正確裝置角色&lt;/a&gt;的部落格文章。</string>
<!-- ROUTING -->
- <string name="routing_error_admin_bad_session_key">無效的會話金鑰</string>
- <string name="routing_error_admin_public_key_unauthorized">無法識別公鑰</string>
- <string name="routing_error_bad_request">錯誤請求</string>
- <string name="routing_error_duty_cycle_limit">已達區域工作週期之上限</string>
<string name="routing_error_got_nak">接收到拒絕確認</string>
- <string name="routing_error_max_retransmit">已達最大重新發送次數</string>
- <string name="routing_error_no_channel">無頻道</string>
- <string name="routing_error_no_interface">無介面</string>
- <string name="routing_error_no_response">無回應</string>
<string name="routing_error_no_route">無路徑</string>
<string name="routing_error_none">已確認</string>
- <string name="routing_error_not_authorized">未授權</string>
- <string name="routing_error_pki_failed">加密發送錯誤</string>
- <string name="routing_error_pki_send_fail_public_key">PKI 傳送失敗，無公開金鑰</string>
- <string name="routing_error_pki_unknown_pubkey">未知公鑰</string>
- <string name="routing_error_rate_limit_exceeded">超過速率限制，請稍後再嘗試。</string>
<string name="routing_error_timeout">逾時</string>
- <string name="routing_error_too_large">封包過大</string>
<string name="rssi">RSSI</string>
<string name="rssi_definition">接收信號強度指示（RSSI）用於測量天線所接收到信號的功率強度。 RSSI 值越高通常代表連線越強且穩定。</string>
<string name="rsyslog_server">rsyslog伺服器</string>

diff --git a/docs/ar-rSA/user/messages-and-channels.md b/docs/ar-rSA/user/messages-and-channels.md
index acdde61891..2f512f2c91 100644
--- a/docs/ar-rSA/user/messages-and-channels.md
+++ b/docs/ar-rSA/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| غلط | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| استغرق وقت طويل | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| لم يجد وسيط | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| لا يوجد قناه | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| طلب غير جيد | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| غلط | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| استغرق وقت طويل | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/be-rBY/user/messages-and-channels.md b/docs/be-rBY/user/messages-and-channels.md
index ebd319dc2b..52936d5cef 100644
--- a/docs/be-rBY/user/messages-and-channels.md
+++ b/docs/be-rBY/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Памылка | Meaning | What to Do |
-| --------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Скончыўся час чакання | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Няма інтэрфейсу | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Няма канала | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Няправільны запыт | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Памылка | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Скончыўся час чакання | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/bg-rBG/user/messages-and-channels.md b/docs/bg-rBG/user/messages-and-channels.md
index fe9d3bcea1..e017a7088d 100644
--- a/docs/bg-rBG/user/messages-and-channels.md
+++ b/docs/bg-rBG/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Грешка | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Няма интерфейс | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Няма канал | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| Няма отговор | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Невалидна заявка | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Грешка | Meaning | What to Do |
+| ---------------------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Съобщението е твърде голямо за изпращане | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/ca-rES/user/messages-and-channels.md b/docs/ca-rES/user/messages-and-channels.md
index 3e39028a54..aecf90b9fb 100644
--- a/docs/ca-rES/user/messages-and-channels.md
+++ b/docs/ca-rES/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Error | Meaning | What to Do |
-| ------------------------------------ | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Temps esgotat | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Sense Interfície | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Sense canal | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Sol·licitud errònia. | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Error | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Temps esgotat | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/cs-rCZ/user/messages-and-channels.md b/docs/cs-rCZ/user/messages-and-channels.md
index c0f60bab7d..89a1759f4f 100644
--- a/docs/cs-rCZ/user/messages-and-channels.md
+++ b/docs/cs-rCZ/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Chyba | Meaning | What to Do |
-| ------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Vypršel čas spojení | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Žádné rozhraní | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Žádný kanál | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| Žádná odpověď | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Špatný požadavek | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Chyba | Meaning | What to Do |
+| ------------------------------------ | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Vypršel čas spojení | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Nepodařilo se doručit do mesh sítě | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Zpráva je příliš dlouhá pro odeslání | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/de-rDE/user/messages-and-channels.md b/docs/de-rDE/user/messages-and-channels.md
index 52282aef60..fbfa2f6172 100644
--- a/docs/de-rDE/user/messages-and-channels.md
+++ b/docs/de-rDE/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Fehler | Meaning | What to Do |
-| ------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Keine Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Zeitlimit erreicht | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Keine Schnittstelle | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Kein Kanal | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| Keine Antwort | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Ungültige Anfrage | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Fehler | Meaning | What to Do |
+| -------------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| Keine Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Zeitlimit erreicht | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Nachricht ist zu groß zum Senden | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/el-rGR/user/messages-and-channels.md b/docs/el-rGR/user/messages-and-channels.md
index 277700677e..95120aef93 100644
--- a/docs/el-rGR/user/messages-and-channels.md
+++ b/docs/el-rGR/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Σφάλμα | Meaning | What to Do |
-| ------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Λήξη χρονικού ορίου | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| No Interface | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Kein Kanal | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Εσφαλμένο Αίτημα | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Σφάλμα | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Λήξη χρονικού ορίου | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/es-rES/user/messages-and-channels.md b/docs/es-rES/user/messages-and-channels.md
index 20aade3a7c..433133d234 100644
--- a/docs/es-rES/user/messages-and-channels.md
+++ b/docs/es-rES/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Error | Meaning | What to Do |
-| ----------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Tiempo agotado | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Sin interfaz | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| No hay canal | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Solicitud errónea | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Error | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Tiempo agotado | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/et-rEE/user/messages-and-channels.md b/docs/et-rEE/user/messages-and-channels.md
index 5d732f6c39..5542b622ed 100644
--- a/docs/et-rEE/user/messages-and-channels.md
+++ b/docs/et-rEE/user/messages-and-channels.md
@@ -73,18 +73,18 @@ Olekumärgis kuvatakse ainult **sinu enda** väljaminevate sõnumite all (teiste
Kui sõnumit ei õnnestu kohale toimetada, näitab veaindikaator, mis valesti läks:
-| Tõrge | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | Järgmise-hüppe sõlm keeldus edastamast | Vahendussõlm võib olla ülekoormatud. Wait and retry. |
-| Aegunud | No acknowledgment within retry window | The recipient may be just out of range. Proovi hüppe limiiti suurendada või paremasse asukohta minna. |
-| Liidest pole | No radio interface available to send | Kontrolli, kas raadio on ühendatud ja kanal on seadistatud. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Proovi teist kanalit või oota, kuni olukord paraneb. |
-| Kanalit pole | Sihtkanalit pole olemas | Veendu, et mõlemal sõlmel oleks sama kanali seadistus. |
-| Too Large | Sõnum ületab maksimaalset sõnumi mahtu | Lühenda oma sõnumit (maksimaalselt ~200 tähemärki). |
-| Vastust pole | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Vigane päring | Malformed or invalid message | This usually indicates a software bug. Proovi rakendust taaskäivitada. |
+| Tõrge | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | Järgmise-hüppe sõlm keeldus edastamast | Vahendussõlm võib olla ülekoormatud. Wait and retry. |
+| Aegunud | No acknowledgment within retry window | The recipient may be just out of range. Proovi hüppe limiiti suurendada või paremasse asukohta minna. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Sõnum ületab maksimaalset sõnumi mahtu | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Vihje:** Enamik kohaletoimetamise vigu laheneb iseenesest. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/fi-rFI/user/messages-and-channels.md b/docs/fi-rFI/user/messages-and-channels.md
index ec9a1c9911..9c0453881e 100644
--- a/docs/fi-rFI/user/messages-and-channels.md
+++ b/docs/fi-rFI/user/messages-and-channels.md
@@ -73,18 +73,18 @@ Tilateksti näkyy vain **omissa** lähtevissä viesteissäsi (muiden lähettämi
Kun viestin toimitus epäonnistuu, virheilmaisin näyttää, mikä meni pieleen:
-| Virhe | Merkitys | Toimenpiteet |
-| ------------------------------------------------------ | ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Ei reittiä | Kohderadioon ei ole reittiä | Vastaanottaja voi olla offline-tilassa tai verkon kantaman ulkopuolella. Yritä myöhemmin tai siirry lähemmäksi. |
-| Hylkäyskuittaus vastaanotettu (NAK) | Seuraavan hypyn radio kieltäytyi välittämästä | Välittäjä-radio voi olla ruuhkautunut. Odota ja yritä uudelleen. |
-| Aikakatkaisu | Ei kuittausta uudelleenyritysten aikana | Vastaanottaja voi olla kantaman ulkopuolella. Yritä nostaa hyppyrajaa tai siirtyä parempaan paikkaan. |
-| Ei Käyttöliittymää | Lähetykseen ei ole käytettävissä radioliitäntää | Tarkista, että radio on yhdistetty ja kanava on määritetty. |
-| Kaikki uudelleenyritykset käytetty | Uudelleenyritysten enimmäismäärä saavutettu | Mesh-reitti ei ole luotettava. Kokeile toista kanavaa tai odota olosuhteiden parantumista. |
-| Ei Kanavaa | Kohdekanavaa ei ole olemassa | Varmista, että molemmilla radioilla on sama kanavakonfiguraatio. |
-| Liian suuri | Viesti ylittää sallitun enimmäiskoon | Lyhennä viestisi (enintään noin 200 merkkiä). |
-| Ei vastausta | Radio vastaanotti viestin mutta ei vastannut | Vastaanottajan radio voi olla varattu tai virransäästötilassa. |
-| Käyttöasteen rajoitus | Alueellinen lähetysajan raja saavutettu | Radiosi on käyttänyt sallitun lähetysajan. Odota, että käyttöasteen rajoituksen ikkuna nollautuu (tyypillisesti 1 tunti EU-alueilla). |
-| Virheellinen pyyntö | Viallinen tai virheellinen viesti | Tämä yleensä viittaa ohjelmistovirheeseen. Kokeile käynnistää sovellus uudelleen. |
+| Virhe | Merkitys | Toimenpiteet |
+| ------------------------------------------------------ | ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
+| Ei reittiä | Kohderadioon ei ole reittiä | Vastaanottaja voi olla offline-tilassa tai verkon kantaman ulkopuolella. Yritä myöhemmin tai siirry lähemmäksi. |
+| Hylkäyskuittaus vastaanotettu (NAK) | Seuraavan hypyn radio kieltäytyi välittämästä | Välittäjä-radio voi olla ruuhkautunut. Odota ja yritä uudelleen. |
+| Aikakatkaisu | Ei kuittausta uudelleenyritysten aikana | Vastaanottaja voi olla kantaman ulkopuolella. Yritä nostaa hyppyrajaa tai siirtyä parempaan paikkaan. |
+| No radio interface | Lähetykseen ei ole käytettävissä radioliitäntää | Check that your radio is connected and available. |
+| Toimitus mesh-verkkoon epäonnistui | Uudelleenyritysten enimmäismäärä saavutettu | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Viesti on liian suuri lähetettäväksi | Viesti ylittää sallitun enimmäiskoon | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Alueellinen lähetysajan raja saavutettu | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 Vinkki: Useimmat toimitusvirheet korjaantuvat itsestään. Jos radio on ajoittain tavoitettavissa, mesh yrittää uudelleen. Jos “Ei reittiä” -virhe toistuu, tarkista että välissä olevat reitittävät radiot ovat verkossa.

diff --git a/docs/fr-rFR/user/messages-and-channels.md b/docs/fr-rFR/user/messages-and-channels.md
index 7d5dc5bbbc..640ba318ed 100644
--- a/docs/fr-rFR/user/messages-and-channels.md
+++ b/docs/fr-rFR/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Erreur | Meaning | What to Do |
-| ------------------------------ | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Pas de route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Délai d'expiration | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Pas d'interface | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Pas de canal ou d'autorisation | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| Pas de réponse | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Mauvaise requête | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Erreur | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| Pas de route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Délai d'expiration | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/ga-rIE/user/messages-and-channels.md b/docs/ga-rIE/user/messages-and-channels.md
index 0511dc0676..679c8309da 100644
--- a/docs/ga-rIE/user/messages-and-channels.md
+++ b/docs/ga-rIE/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Earráid | Meaning | What to Do |
-| ----------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Am tráth | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Gan anicéir | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Gan cainéal | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Iarratas Mícheart | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Earráid | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Am tráth | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/gl-rES/user/messages-and-channels.md b/docs/gl-rES/user/messages-and-channels.md
index 514538ff3a..deed01c4f4 100644
--- a/docs/gl-rES/user/messages-and-channels.md
+++ b/docs/gl-rES/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Erro | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| No Interface | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| No Channel | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Bad Request | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Erro | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/hr-rHR/user/messages-and-channels.md b/docs/hr-rHR/user/messages-and-channels.md
index 736a9b2921..ea232e620a 100644
--- a/docs/hr-rHR/user/messages-and-channels.md
+++ b/docs/hr-rHR/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Pogreška | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| No Interface | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| No Channel | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Bad Request | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Pogreška | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/ht-rHT/user/messages-and-channels.md b/docs/ht-rHT/user/messages-and-channels.md
index 54e4b15eb7..f0a2dd2ad4 100644
--- a/docs/ht-rHT/user/messages-and-channels.md
+++ b/docs/ht-rHT/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Erè | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Tan pase | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Pa gen entèfas | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Pa gen kanal | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Demann move | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Erè | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Tan pase | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/hu-rHU/user/messages-and-channels.md b/docs/hu-rHU/user/messages-and-channels.md
index 22da6bd38b..0769db7f6f 100644
--- a/docs/hu-rHU/user/messages-and-channels.md
+++ b/docs/hu-rHU/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Hiba | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Időtúllépés | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Nincs Interfész | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Nincs Csatorna | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Hibás kérés | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Hiba | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Időtúllépés | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/is-rIS/user/messages-and-channels.md b/docs/is-rIS/user/messages-and-channels.md
index 5b6ba5e942..ab41bd9bb0 100644
--- a/docs/is-rIS/user/messages-and-channels.md
+++ b/docs/is-rIS/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Error | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| No Interface | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| No Channel | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Bad Request | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Error | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/it-rIT/user/messages-and-channels.md b/docs/it-rIT/user/messages-and-channels.md
index c83f9a0099..e72c9fbde5 100644
--- a/docs/it-rIT/user/messages-and-channels.md
+++ b/docs/it-rIT/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Errori | Meaning | What to Do |
-| -------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Nessuna Interfaccia | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Nessun Canale | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Richiesta Non Valida | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Errori | Meaning | What to Do |
+| ----------------------------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Consegna alla mesh non riuscita | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Il messaggio è troppo grande per essere inviato | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/iw-rIL/user/messages-and-channels.md b/docs/iw-rIL/user/messages-and-channels.md
index 44d2cdfc13..d90dc42c7e 100644
--- a/docs/iw-rIL/user/messages-and-channels.md
+++ b/docs/iw-rIL/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| שגיאה | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| No Interface | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| No Channel | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Bad Request | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| שגיאה | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/ja-rJP/user/messages-and-channels.md b/docs/ja-rJP/user/messages-and-channels.md
index a431b2a22a..4011a7d3df 100644
--- a/docs/ja-rJP/user/messages-and-channels.md
+++ b/docs/ja-rJP/user/messages-and-channels.md
@@ -73,18 +73,18 @@ Meshtastic は、**チャンネルブロードキャスト**と**ダイレクト
メッセージの配信に失敗すると、エラーインジケーターが何が問題だったかを示します：
-| エラー | 意味 | 対処方法 |
-| -------------- | --------------------------- | ------------------------------------------------------------------------ |
-| ルートなし | 宛先ノードへの経路が存在しません | 受信者がオフラインか、メッシュの範囲外の可能性があります。 時間をおくか、距離を縮めてください。 |
-| NAK を受信 | 次のホップのノードが中継を拒否しました | 中継ノードが混雑している可能性があります。 しばらく待ってから再試行してください。 |
-| タイムアウト | 再試行の時間内に受信確認がありませんでした | 受信者がちょうど範囲外にいる可能性があります。 ホップ数上限を増やすか、より良い場所に移動してみてください。 |
-| インターフェースがありません | 送信に使える無線インターフェースがありません | 無線機が接続され、チャンネルが設定されているか確認してください。 |
-| 最大再送回数 | すべての再試行を使い切りました | メッシュ経路が不安定です。 別のチャンネルを試すか、状況が改善するのを待ってください。 |
-| チャンネルがありません | 宛先のチャンネルが存在しません | 両方のノードが同じチャンネル設定を共有しているか確認してください。 |
-| サイズ超過 | メッセージが最大ペイロードサイズを超えています | メッセージを短くしてください（最大約 200 文字）。 |
-| 応答なし | ノードはメッセージを受信しましたが、応答しませんでした | 受信者の無線機が処理中か、低電力のスリープモードの可能性があります。 |
-| デューティサイクル制限 | 地域ごとの電波利用時間の上限に達しました | 無線機が許可された送信時間を使い切りました。 デューティサイクルの期間がリセットされるまで待ってください（EU リージョンでは通常 1 時間）。 |
-| 不正な要求 | 不正な形式または無効なメッセージです | 通常はソフトウェアの不具合を示します。 アプリを再起動してみてください。 |
+| エラー | 意味 | 対処方法 |
+| -------------------- | -------------------------------------------- | ------------------------------------------------------------------------------------ |
+| ルートなし | 宛先ノードへの経路が存在しません | 受信者がオフラインか、メッシュの範囲外の可能性があります。 時間をおくか、距離を縮めてください。 |
+| NAK を受信 | 次のホップのノードが中継を拒否しました | 中継ノードが混雑している可能性があります。 しばらく待ってから再試行してください。 |
+| タイムアウト | 再試行の時間内に受信確認がありませんでした | 受信者がちょうど範囲外にいる可能性があります。 ホップ数上限を増やすか、より良い場所に移動してみてください。 |
+| No radio interface | 送信に使える無線インターフェースがありません | Check that your radio is connected and available. |
+| メッシュへの配信に失敗しました | すべての再試行を使い切りました | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| メッセージが大きすぎて送信できません | メッセージが最大ペイロードサイズを超えています | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | 地域ごとの電波利用時間の上限に達しました | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **ヒント：** ほとんどの配信エラーは自然に解消します。 ノードに断続的に到達できる場合、メッシュは再試行します。 「ルートなし」エラーが続く場合は、中間のルーターノードがオンラインになっているか確認してください。

diff --git a/docs/ko-rKR/user/messages-and-channels.md b/docs/ko-rKR/user/messages-and-channels.md
index 72877cb1c5..bcfa8e3fdb 100644
--- a/docs/ko-rKR/user/messages-and-channels.md
+++ b/docs/ko-rKR/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Error | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| 시간 초과 | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| 인터페이스 없음 | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| 채널 없음 | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| 잘못된 요청 | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Error | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| 시간 초과 | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/lt-rLT/user/messages-and-channels.md b/docs/lt-rLT/user/messages-and-channels.md
index dddd93e889..cee2dbe36f 100644
--- a/docs/lt-rLT/user/messages-and-channels.md
+++ b/docs/lt-rLT/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Klaida | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Baigėsi laikas | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Nėra sąsajos | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Nėra kanalo | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Bloga užklausa | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Klaida | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Baigėsi laikas | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/nl-rNL/user/messages-and-channels.md b/docs/nl-rNL/user/messages-and-channels.md
index e16a2a8599..c5e51014aa 100644
--- a/docs/nl-rNL/user/messages-and-channels.md
+++ b/docs/nl-rNL/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Foutmelding | Meaning | What to Do |
-| ------------------ | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Time-Out | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Geen Interface | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Geen Kanaal | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Ongeldige aanvraag | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Foutmelding | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Time-Out | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/no-rNO/user/messages-and-channels.md b/docs/no-rNO/user/messages-and-channels.md
index c7a52c46eb..4e27cd6f97 100644
--- a/docs/no-rNO/user/messages-and-channels.md
+++ b/docs/no-rNO/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Feil | Meaning | What to Do |
-| ------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Tidsavbrudd | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Ingen grensesnitt | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Ingen Kanal | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Ugyldig Forespørsel | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Feil | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Tidsavbrudd | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/pl-rPL/user/messages-and-channels.md b/docs/pl-rPL/user/messages-and-channels.md
index f5b7f4a077..19b22d7120 100644
--- a/docs/pl-rPL/user/messages-and-channels.md
+++ b/docs/pl-rPL/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Błąd | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Brak trasy | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Limit czasu | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Brak interfejsu | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Brak kanału | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| Brak odpowiedzi | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Złe żądanie | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Błąd | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| Brak trasy | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Limit czasu | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/pt-rBR/user/messages-and-channels.md b/docs/pt-rBR/user/messages-and-channels.md
index db52d5defb..0e4b570dd6 100644
--- a/docs/pt-rBR/user/messages-and-channels.md
+++ b/docs/pt-rBR/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Erro | Meaning | What to Do |
-| ------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Tempo esgotado | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Sem interface | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Nenhum canal | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Requisição Inválida | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Erro | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Tempo esgotado | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/pt-rPT/user/messages-and-channels.md b/docs/pt-rPT/user/messages-and-channels.md
index ac1ce93dc2..8f0d6c279b 100644
--- a/docs/pt-rPT/user/messages-and-channels.md
+++ b/docs/pt-rPT/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Erros | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Sem interface | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Sem canal | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Pedido Inválido | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Erros | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/ro-rRO/user/messages-and-channels.md b/docs/ro-rRO/user/messages-and-channels.md
index 662a09e8fd..444b3b535a 100644
--- a/docs/ro-rRO/user/messages-and-channels.md
+++ b/docs/ro-rRO/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Eroare | Meaning | What to Do |
-| ------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Expirat | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Fără interfață | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Niciun canal | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| Niciun raspuns | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Solicitare invalidă | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Eroare | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Expirat | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/ru-rRU/user/messages-and-channels.md b/docs/ru-rRU/user/messages-and-channels.md
index 94fa749640..e4e5f5851b 100644
--- a/docs/ru-rRU/user/messages-and-channels.md
+++ b/docs/ru-rRU/user/messages-and-channels.md
@@ -73,18 +73,18 @@ Meshtastic поддерживает два режима связи: **вещан
Когда сообщение не удаётся доставить, индикатор ошибки показывает, что пошло не так:
-| Ошибки | Значение | Что делать |
-| ---------------------------- | --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Нет маршрута | Путь к целевой ноде отсутствует | Получатель может быть не в сети или вне зоны действия mesh-сети. Повторите попытку позже или подойдите ближе. |
-| Получен NAK | Следующая нода отказалась ретранслировать | Ретранслирующая нода может быть перегружена. Подождите и повторите попытку. |
-| Время ожидания истекло | Нет подтверждения в пределах окна повторных попыток | Получатель, возможно, находится сразу за пределами зоны досягаемости. Попробуйте увеличить лимит хопов или переместиться в место с лучшим сигналом. |
-| Нет интерфейса | Нет доступного радиоинтерфейса для отправки | Проверь, подключено ли твоё радио и настроен ли канал. |
-| Исчерпаны повторные передачи | Все попытки повторной отправки исчерпаны | Путь в mesh-сети ненадёжен. Попробуйте другой канал или дождитесь улучшения условий. |
-| Нет канала | Канал назначения не существует | Убедитесь, что обе ноды используют одинаковую конфигурацию канала. |
-| Слишком большое | Сообщение превышает максимальный размер полезной нагрузки | Сократите сообщение (максимум ~200 символов). |
-| Без ответа | Нода получила сообщение, но не ответила | Радио получателя может быть занято или находиться в спящем режиме с низким энергопотреблением. |
-| Ограничение рабочего цикла | Достигнут региональный лимит эфирного времени | Твоё радио исчерпало разрешённое время передачи. Дождитесь сброса окна рабочего цикла (обычно 1 час в регионах ЕС). |
-| Неверный запрос | Повреждённое или недействительное сообщение | Обычно это указывает на программную ошибку. Попробуйте перезапустить приложение. |
+| Ошибки | Значение | Что делать |
+| -------------------------------------- | --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Нет маршрута | Путь к целевой ноде отсутствует | Получатель может быть не в сети или вне зоны действия mesh-сети. Повторите попытку позже или подойдите ближе. |
+| Получен NAK | Следующая нода отказалась ретранслировать | Ретранслирующая нода может быть перегружена. Подождите и повторите попытку. |
+| Время ожидания истекло | Нет подтверждения в пределах окна повторных попыток | Получатель, возможно, находится сразу за пределами зоны досягаемости. Попробуйте увеличить лимит хопов или переместиться в место с лучшим сигналом. |
+| No radio interface | Нет доступного радиоинтерфейса для отправки | Check that your radio is connected and available. |
+| Не удалось доставить в сеть | Все попытки повторной отправки исчерпаны | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Слишком большое сообщение для отправки | Сообщение превышает максимальный размер полезной нагрузки | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Достигнут региональный лимит эфирного времени | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Совет:** Большинство ошибок доставки разрешаются сами собой. Если нода доступна с перебоями, mesh-сеть будет повторять попытки. При постоянных ошибках «Нет маршрута» проверьте, что промежуточные ноды-роутеры находятся в сети.

diff --git a/docs/sk-rSK/user/messages-and-channels.md b/docs/sk-rSK/user/messages-and-channels.md
index b97add399a..fd19d6e2e7 100644
--- a/docs/sk-rSK/user/messages-and-channels.md
+++ b/docs/sk-rSK/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Chyba | Meaning | What to Do |
-| -------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Časový limit | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Žiadne rozhranie | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Žiaden kanál | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Nesprávna požiadavka | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Chyba | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Časový limit | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/sl-rSI/user/messages-and-channels.md b/docs/sl-rSI/user/messages-and-channels.md
index 60df757a2f..64a4c54e28 100644
--- a/docs/sl-rSI/user/messages-and-channels.md
+++ b/docs/sl-rSI/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Napaka | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Časovna omejitev | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Brez vmesnika | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Brez kanala | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Slaba zahteva | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Napaka | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Časovna omejitev | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/sq-rAL/user/messages-and-channels.md b/docs/sq-rAL/user/messages-and-channels.md
index 9dac6be81f..7220da7339 100644
--- a/docs/sq-rAL/user/messages-and-channels.md
+++ b/docs/sq-rAL/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Gabim | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Koha e skaduar | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Nuk ka ndërfaqe | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Nuk ka kanal | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Kërkesë e gabuar | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Gabim | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Koha e skaduar | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/sr-rLatn/user/messages-and-channels.md b/docs/sr-rLatn/user/messages-and-channels.md
index e16c5ad83c..a61e606edb 100644
--- a/docs/sr-rLatn/user/messages-and-channels.md
+++ b/docs/sr-rLatn/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Грешка | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Нема руте | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Isteklo vreme | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Nema interfejsa | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Nema kanala | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| Нема одговора | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Loš zahtev | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Грешка | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| Нема руте | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Isteklo vreme | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/srp/user/messages-and-channels.md b/docs/srp/user/messages-and-channels.md
index f3446810ef..1237c54f9e 100644
--- a/docs/srp/user/messages-and-channels.md
+++ b/docs/srp/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Грешка | Meaning | What to Do |
-| -------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Нема руте | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Временско ограничење | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Нема интерфејса | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Нема канала | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| Нема одговора | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Лош захтев | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Грешка | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| Нема руте | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Временско ограничење | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/sv-rSE/user/messages-and-channels.md b/docs/sv-rSE/user/messages-and-channels.md
index 09ad075431..289e09a5a5 100644
--- a/docs/sv-rSE/user/messages-and-channels.md
+++ b/docs/sv-rSE/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Fel | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Inget gränssnitt | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Ingen kanal | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| Inget svar | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Misslyckad | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Fel | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/tr-rTR/user/messages-and-channels.md b/docs/tr-rTR/user/messages-and-channels.md
index 0fa445c92b..6b346d19d9 100644
--- a/docs/tr-rTR/user/messages-and-channels.md
+++ b/docs/tr-rTR/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Hata | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Zaman Aşımı | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Arayüz Yok | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Kanal yok | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Geçersiz İstek | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Hata | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Zaman Aşımı | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/uk-rUA/user/messages-and-channels.md b/docs/uk-rUA/user/messages-and-channels.md
index 1f00d5963a..498bff5935 100644
--- a/docs/uk-rUA/user/messages-and-channels.md
+++ b/docs/uk-rUA/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| Error | Meaning | What to Do |
-| ------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| Таймаут | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| Інтерфейс відсутній | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| Канал відсутній | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| Немає відповіді | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| Невірний запит | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| Error | Meaning | What to Do |
+| ---------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| Таймаут | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| Failed to deliver to mesh | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/zh-rCN/user/messages-and-channels.md b/docs/zh-rCN/user/messages-and-channels.md
index 0ff8ed73c6..0718922c09 100644
--- a/docs/zh-rCN/user/messages-and-channels.md
+++ b/docs/zh-rCN/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
When a message fails to deliver, the error indicator shows what went wrong:
-| 错误 | Meaning | What to Do |
-| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 找不到目标 | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
-| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
-| 超时 | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
-| 无连接 | No radio interface available to send | Check that your radio is connected and the channel is configured. |
-| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
-| 没有频道 | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
-| Too Large | Message exceeds maximum payload size | Shorten your message (max ~200 characters). |
-| 无响应 | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
-| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
-| 错误请求 | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
+| 错误 | Meaning | What to Do |
+| -------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| 找不到目标 | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
+| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
+| 超时 | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
+| No radio interface | No radio interface available to send | Check that your radio is connected and available. |
+| 发送至MESH失败 | All retry attempts exhausted | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| 消息太大，无法发送 | Message exceeds maximum payload size | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.

diff --git a/docs/zh-rTW/user/messages-and-channels.md b/docs/zh-rTW/user/messages-and-channels.md
index cd197115f5..a9529ea041 100644
--- a/docs/zh-rTW/user/messages-and-channels.md
+++ b/docs/zh-rTW/user/messages-and-channels.md
@@ -73,18 +73,18 @@ A status label appears under **your own** outgoing messages only (incoming messa
當訊息傳遞失敗時，錯誤指示器將顯示問題原因：
-| 錯誤 | 含義 | 處理方式 |
-| ------------ | ------------- | ---------------------------------------------------------------------------------------------- |
-| 無路由 | 無法找到通往目標節點的路徑 | 收件者可能已離線或超出 mesh 網路範圍。 請稍後再試，或靠近對方後重新傳送。 |
-| 收到 NAK | 下一個跳躍點節點拒絕轉送 | 中繼節點可能發生壅塞。 請稍候後重試。 |
-| Timeout - 超時 | 在重試時間內未收到確認回應 | 收件者可能剛好超出訊號範圍。 請嘗試提高跳躍限制，或移動至訊號較佳的位置。 |
-| 無介面 | 無可用的無線電介面進行傳送 | 請確認無線電裝置已連線，且頻道已正確設定。 |
-| 已達最大重傳次數 | 所有重試次數均已用盡 | Mesh 網路路徑不穩定。 請嘗試切換至其他頻道，或等待網路狀況改善。 |
-| 無頻道 | 目標頻道不存在 | 請確認兩個節點使用相同的頻道設定。 |
-| 訊息過大 | 訊息超過最大承載大小 | Shorten your message (max ~200 characters). |
-| 無回應 | 節點已收到訊息但未回應 | 收件者的無線電裝置可能正忙碌，或處於低功耗睡眠模式。 |
-| 佔空比限制 | 已達地區無線電佔用時間上限 | 您的無線電裝置已用完允許的傳輸時間。 請等待佔空比時間窗口重設（在歐盟地區通常為 1 小時）。 |
-| 錯誤請求 | 格式錯誤或無效的訊息 | 這通常表示存在軟體錯誤。 請嘗試重新啟動應用程式。 |
+| 錯誤 | 含義 | 處理方式 |
+| ---------------------------- | -------------------------------------------- | ------------------------------------------------------------------------------------ |
+| 無路由 | 無法找到通往目標節點的路徑 | 收件者可能已離線或超出 mesh 網路範圍。 請稍後再試，或靠近對方後重新傳送。 |
+| 收到 NAK | 下一個跳躍點節點拒絕轉送 | 中繼節點可能發生壅塞。 請稍候後重試。 |
+| Timeout - 超時 | 在重試時間內未收到確認回應 | 收件者可能剛好超出訊號範圍。 請嘗試提高跳躍限制，或移動至訊號較佳的位置。 |
+| No radio interface | 無可用的無線電介面進行傳送 | Check that your radio is connected and available. |
+| Failed to deliver to mesh | 所有重試次數均已用盡 | Move closer, improve signal, or wait for mesh conditions to improve. |
+| Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. |
+| Message is too large to send | 訊息超過最大承載大小 | Shorten the message and try again. |
+| No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. |
+| Duty cycle limit | 已達地區無線電佔用時間上限 | Wait for the duty cycle window to reset. |
+| Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. |
> 💡 提示：大多數傳遞錯誤會自動解決。 若節點間歇性可到達，mesh 網路將自動重試。 若持續出現「無路由」錯誤，請確認中間的路由器節點是否在線。

Served by rngit 1.5.2 - Generated in 1.0s